OrientDB - Perché le tue applicazioni meritano un DB Multi-Model

DevDay Napoli

And why GraphDB are the starting point of this revolution

- the 2nd generation of

(Multi-Model) NoSQLAnd why GraphDB are the

starting point of this revolution

DevDay Napoli

29/10 ore 16.00 - Bootstrap 4 & SASS (Js&Node Meetup Salerno)

30/11 ore 18.45 - OAuthorize yourself 2.0 - dalla crittografia ai protocolli web (DevDay Napoli)

Prossimi Eventi

#OrientDB - @ldellaquila

Luigi Dell’AquilaCore Developer and Director of ConsultingOrientDB LTDTwitter: @ldellaquilahttp://www.orientdb.com

“90% of the data in the world today has been created in the last two years alone.”

Order #134 (Order) John

(Provider)

Commodore Amiga 1200

(Product)

Frank (Customer)

Monitor 40” (Product)

Mouse (Product)

Bruno (Provider)

(Provider)

(Product)

Frank (Customer)

Mouse (Product)

Bruno (Provider)

Data by itself has little value, it’s the relationship

between data that gives it incredible value

(Provider)

(Product)

(Sells)

Frank (Customer)

(Has)(Makes)

(Sells)(Has)

Mouse (Product)

Bruno (Provider)

(Sells)

Key/Value DatabasesDocument Databases

Graph DatabasesColumn Databases

Key/Value Databases

Document Databases Graph Databases

Column Databases

Why do most NoSQL products avoid

managing relationships?

ID Name

10 John

11 John

24 Mike

28 Mike

ID Address

ID Location

24 Milan

33 London

18 Paris

18 Madrid

44 Moscow

Customer CustomerAddress Address

Is this familiar?

What’swrongwithJOIN?

ID Name

10 John

11 John

24 Mike

28 Mike

ID Address

ID Location

24 Milan

33 London

18 Paris

18 Madrid

44 Moscow

Customer CustomerAddress AddressJoins are executed every time

you cross relationships

Querying millions of records joining 3-4 tables could

generate billions of combinations

This is why the database query performance

suffers as the database increases in size

O(Log N)

PERFORMANCE

DATABASE SIZE

RDBMS performance on traversal

Solution: Graph Database!

Back to school: Graph Theory crash course

Basic Graph

Luigi RomeVisited

VerticesandEdgescanhaveproperties

Verticesaredirected

*https://github.com/tinkerpop/blueprints/wiki/Property-Graph-Model

Property Graph Model*

Romecountry:Italy

Luigicompany:OrientDB

VerticesandEdgescanhaveproperties

Visitedyear:2016

Luigi Rome

Visitedyear:2016

AnEdgeconnectsonly2vertices

Usemultipleedgestorepresent1-NandN-Mrelationships

Workedyear:2016

1-N and N-M Relationships

Congrats! This is your diploma in «Graph Theory»

How does a true* Graph Database

manage relationships?

*a “Graph” layer on top of a DBMS doesn’t qualify as a true GraphDB

Luigi Rome

Visitedyear:2015

#13:55#15:99

Each element in the Graph has own immutable

Record ID

#22:11

(Edge)

(Vertex)(Vertex)

Record ID

Connections use persistent pointers

Luigi Rome

Visitedon:2015

#13:55#15:99out = #22:11

in = #22:11

#22:11

(Edge)

(Vertex)(Vertex)

out = #13:55

in = #15:99

Luigi Rome

Visitedon:2015

#13:55#15:99out = #22:11

in = #22:11

#22:11

(Edge)

(Vertex)(Vertex)

out = #13:55

in = #15:99

Luigi Rome

Visitedon:2015

#13:55#15:99out = #22:11

in = #22:11

#22:11

(Edge)

(Vertex)(Vertex)

out = #13:55

in = #15:99

A Graph Database creates the relationship just once

(when the edge is created)

RDBMS computes the relationship every time you query a database

When you move from a RDBMS to a Graph Database you jump

from a O(log N) speed to a near O(1)

With a Graph Database, the traversing time is

not affected by database size!

This is huge in the BigData age

No costs to traverse relationships: • Recommendation engines • Social Applications • Spatial Apps • Master Data Management • Information Clustering

Thriller

Comedy

Pulp Fiction

Mr Bean

Theater B

Theater A

Theater C

San Josè

Lives in

So the Graph Model Is the only solution to efficiently

manage relationships

But what about data complexity? And data consistency?

And scaling?

Data Complexity >

Relational

Key Value

Column

Document

First Generation NoSQL

Key/ValueStore

DocumentDatabase

GraphDatabase

Application

Primary DB

Key/ValueStore

DocumentDatabase

GraphDatabase

Application

- No standard between NoSQL products - Multiple vendors = multiple skills - ETL + synchronization code is costly to write and maintain - Performance and Reliability is hard to predict

2nd Generation NoSQL is

Multi-model

GraphDocument

Object

Key/Value

Multi Model represents the intersection

of multiple models in just one product

What’s Multi-Model DBMS?

GraphDocument

Object

Key/Value

Multi Model represents the intersection

of multiple models in just one product

- Just one product to learn and maintain - Just one vendor relationship to manage - No ETL, no synchronization required - Performance and Reliability is easy to test from the beginning

What’s Multi-Model DBMS?

{ ”@rid": “12:382”, ”@class": ”Customer", “name”: “Frank”, “surname” : “Raggio”, “phone” : “+39 33123212”, “details”: { “city”:”London", “tags”:”millennial” } }

General purpose solution: • JSON • Schema-less • Schema-full • Schema-hybrid • Nested documents • Rich indexing and querying • Developer friendly

Second Generation NoSQLRelationship Complexity >

Data Complexity >

Relational

Key Value

Column

Document

Multi-Model

With a true Graph, Document, Key/Value and Object Oriented engine

•Support for TinkerPop standard for Graph DB: Gremlin language and Blueprints API

•SQL + extensions for graphs•JDBC driver to connect any BI tool•HTTP/JSON support•Drivers in Java, Node.js, Python,

PHP, .NET, Perl, C/C++ and more

API & Standards

• Basic HTTP authentication (+HTTPS/SSL)

• User/Role authentication system. One User can have multiple Roles

• Privileges are managed in Roles

• Roles can inherit from other Roles

• Record-level security: every record can contain the user/role can create/read/update/delete the record

• Auditing available in Enterprise Edition

Security

• HTTPS/SSL

• Starting from OrientDB v2.2:• Support for Kerberos• Encryption at REST using AES and DES of the entire

database or portions• PBKDF2 HASH algorithm with a 24-bit length Salt per

user for a configurable number of iterations.

Encryption

• Full Backup and Restore

• Delta Backup (v2.2) Enterprise Edition and Restore is available

• Studio web tool

• Command line Console

Administration

• Import/Export in JSON

• Import from SQL script

• OrientDB ETL tool (http://orientdb.com/docs/last/ETL-Introduction.html)

• Teleporter (v2.2)

Data Extraction and Loading

• Multi-Master architecture

• Tunable consistency through the usage of a quorum, per database or single class (table)

• Synchronous and Asynchronous replication

• Zero config: if multicast is enabled the server is attached to the cluster

Scale out and HA

Master Node Master Node

Multi-master Replication

Atomic, Consistent, Isolated and Durable (ACID) multi-statement transactions

Master Node Master Node

CC C C

Auto-Discovered

Architectures

•  Single, stand-alone node

•  Embedded (in-process) DB

•  Multi-Master Replica

•  Mixed

DB Application

Application DB

Application

DB Application Application DB DB

(replica N)

DB Application Application DB DB

Application

(replica N)

FEATURES ORIENTDB)) MONGODB NEO4J MYSQL)(RDBMS)

Operational Database X X X Graph Database X X Document Database X X Object-Oriented Concepts X Schema-full, Schema-less, Schema mix X User and Role & Record Level Security X Record Level Locking X X X SQL X X ACID Transaction X X X Relationships (Linked Documents) X X X Custom Data Types X X X Embedded Documents X X Multi-Master Zero Configuration Replication X Sharding X X Server Side Functions X X X Native HTTP Rest/ JSON X X Embeddable with No Restrictions X

Udemy Getting Started Training is and Free

http://www.orientechnologies.com/getting-started

OrientDB Enterprise is Free for Development

OrientDB Community is FREE for any purpose (APACHE 2 license)

Thank you!Luigi Dell’Aquila@ldellaquilahttp://www.orientdb.com

OrientDB - Perché le tue applicazioni meritano un DB Multi-Model

Software

Mode d'emploi pour l'installation SQL Server 2016 ... · Mode d'emploi pour l'installation SQL Server 2016 Migration OrientDB en SQL Server et Dr. Tax Office Serveur

Travailler tue - Cefedem AuRA

Éric Barsi – CerTICa 2013 La réflexion ne tue pas

Méga quizz de la mort qui tue

Tuer le stress avant quil ne nous tue ! Distorsions cognitives

Le documentaire qui tue - securite-routiere.org

La lettre tue - Claude et Julia Payan

Aymé, Marcel - Les Contes Du Chat Perché -- Ebook french Clan9

ÇA TUE ÇA EMPOISONNE ÇA PIQUE ÇA EXPLOSE

“Comme Un Papier Tue-mouches Dans Une Maison

FESTIVAL 1 7 LE BARON PERCHÉ L’ECHO DU MARAIS LE Marais …

Portfolio chat Perché

Alors elle s'était tue - Nino Laisné [2007-2013]

TUE 99,9 % DES GERMES EN 60 SECONDES

Alla mia Famiglia, A Mario, perché è molto più che …tesi.luiss.it/22506/1/126453_VALENTI_LUDOVICA_Il...1 Alla mia Famiglia, perché mi ha fatto dono del mondo intero e continua

Le baron perché - Numilog · Tout comme l’était l’Europe des Lumières qui lui sert de cadre stylistique et en partie d’univers de réfé-rence, Le baron perché est un roman

Dr. Tax Office Serveur avec ORIENTDB (remplace H2) max. 250

La question qui tue

Le Théâtre Perché...Saison 2019-2020 Le Théâtre Perché accueillera Le fossoyeur par Franck Sylvestre d'après Chroniques des sept misères de Patrick Chamoiseau Un spectacle

À tue-tête à Voix de fête 2016