Presentation of OrientDB v2.2 - Webinar

What’s New in OrientDB v2.2?
Next Generation DBMS with a Native Multi-Model Engine
Luca Garulli, CEO and Founder

What’s OrientDB?
Quick Overview

Confidential
The OrientDB Journey
1998 2009 2010 2011 20152012 20142013
Orient ODBMS: First
ever ODBMS with
index-free adjacency
OrientDB: First ever
multi-model DBMS
released as Open
Source
AdoptionR&D
2016
0
12K
70K
3K
1K
200
Downloads/m
v2.2 is GA!
(May 18, 2016)

OrientDB is a Multi-Model DBMS
Object
Key/Valu
e
Multi-Model represents the
intersection
of multiple models in just one
product

Confidential
Polyglot vs Multi-Model
Polyglot (NoSQL 1.0) Multimodel (NoSQL 2.0)
Polyglot Persistence is a fancy term to mean that
when storing data, it is best to use multiple data
storage technologies, chosen based upon the
way data is being used by individual applications
or components
Multi-model databases are intended to offer the
data modelling advantages of polyglot persistence
without its disadvantages. complexity, in
particular, is reduced. The first multi-model
database was OrientDB.
https://en.wikipedia.org/wiki/Multi-model_databasehttp://www.jamesserra.com/archive/2015/07/what-is-polyglot-persistence/
ECOMMERCE
PRODUCT CATALOG
SHOPPING
CART
RECOMMENDATI
ON
ECOMMERCE
PRODUCT CATALOG
SHOPPING
CART
RECOMMENDATI
ON
TRANSACTIONA
L TRANSACTIONA
L
SEARCH
SEARCH
SPATIAL
SPATIAL

Confidential
Complexity Quadrant
RelationshipComplexity>
Data Complexity >
Relational
Key Value
Column
Graph
Document
Multi-Model

Confidential
Increasing Global Footprint
OrientDB climbed 24 positions on the DB-Engines.com ranking
being the technology with the highest year-on-year growth
within the top 50.

OrientDB Stability
Quality and Transparency

Confidential
Quality & Transparency - Code Coverage
• OrientDB is the only DBMS with Code Coverage public metrics
• Code Coverage (line) from 55% of v2.1 to 66% of v2.2 (consider that
the code base grew also)

Confidential
Quality & Transparency - Issues
Considering the functionality/complexity of OrientDB, our open bugs
are significantly lower than the average of other Open Source DBMSs

Confidential
24x7 Support Service
We introduced 24x7 support with 2h SLA.
(>60% of our existing clients upgraded from 10x5 to 24x7)

Confidential
Live Query
Typical scenario: Poll the database to check for updates
Problem 1:
Execute many requests
consuming resources
Problem 2:
No real-time
notification

Confidential
Live Query - Action!
Live Query allows you to work in Reactive Mode:
the DBMS pushes updates to the client
Much less
resources consumed
Real-time
notification

Confidential
Live Query - SQL Example
Receives all the updates on any order
LIVE SELECT FROM Order
Receives all the updates only for orders placed in Austin
LIVE SELECT FROM Order WHERE address.city = ‘Austin’
Receives updates when any stocks has an update of >1$
LIVE SELECT FROM Stock WHERE variationUSD > 1
Receives updates when any arriving flights have delays
LIVE SELECT FROM ArrivingFlights where delay > 0

Confidential
Live Query - Java Example
class MyLiveQueryListener implements OLiveResultListener {
public List<ORecordOperation> ops = new ArrayList<ORecordOperation>();
@Override
public void onLiveResult(int iLiveToken, ORecordOperation iOp)
throws OException {
System.out.println("New result from server for live query "+iLiveToken);
System.out.println("operation: "+iOp.type);
System.out.println("content: "+iOp.record);
}
public void onError(int iLiveToken) { }
public void onUnsubscribe(int iLiveToken) { }
}
// Instantiate the query listener
MyLiveQueryListener listener = new MyLiveQueryListener();
// Execute the query
List<ODocument> result = db.query(new OLiveQuery<ODocument>(
"live select from Test", listener));

Confidential
Live Query - Node.js Example
var OrientDB = require('orientjs');
var server = OrientDB({host: 'localhost', port: 2424});
var db = server.use({name: 'test', username: 'admin', password: 'admin'});
db.liveQuery("live select from V”)
.on('live-insert', function(data){
//new record inserted in the database,
var myRecord = data.content;
// your code here...
})
.on('live-delete', function(data){
//record just deleted, receiving the old content
})
.on('live-update', function(data){
//record updated, receiving the new content
})

Confidential
For more information look at: http://orientdb.com/docs/last/Release-2.2.0.html#parallel-queries
Parallel Query
SELECT FROM V WHERE amount < 100 PARALLEL
Activate:
• query.parallelAuto enable automatic parallel query, if requirements are met. By
default is false
Tuning:
• query.parallelMinimumRecords is the minimum number of records to activate
parallel query automatically. Default is 300,000
• query.parallelResultQueueSize is the size of the queue that holds results on
parallel execution. The queue is blocking, so in case the queue is full, the query
threads will be in a wait state. Default is 20,000 results
Manual usage
Automatic usage

Confidential
Command Cache
Use it only if:
• The Database is mostly reads (compared to writes)
• There are a few heavy queries that result in small result sets
• You have available RAM to use for caching results
Stored under: databases/<your-db>/command-cache.json
Default content:
{
"enabled": false,
"evictStrategy": "PER_CLUSTER",
"minExecutionTime": 10,
"maxResultsetSize": 500
}
For more information, look at http://orientdb.com/docs/last/Command-Cache.html.
PER_CLUSTER: removes all the query results
only related to the modified cluster. This
operation is more expensive then
INVALIDATE_ALL
INVALIDATE_ALL removes all the query results
at every Create, Update and Delete operation.
This is faster than PER_CLUSTER if many
writes occur.

Confidential
Command Cache - Studio

Confidential
Sequences
Like with an RDBMS, this allows you to keep counters. Example:
CREATE SEQUENCE idseq
CREATE SEQUENCE mySequence TYPE CACHED START 1000 INCREMENT 1 CACHE 50
INSERT INTO account SET id = sequence('mySequence').next()
ALTER SEQUENCE mySequence START 10000
DROP SEQUENCE mySequence
They can be created as:
•ORDERED (default) each call to .next() will result in a new value
•CACHED, the sequence will cache N items on each node, thus improving the performance if
many .next() calls are required. However, this may create holes
For more information look at: http://orientdb.com/docs/last/Sequences-and-auto-increment.html.

Confidential
Incremental Backup
orientdb> connect plocal:/databases/mydb admin admin
orientdb {db=Whisky}> backup database /tmp/backup -incremental
The incremental backup setting also allows you to specify an LSN version to start with. Example:
orientdb {db=Whisky}> backup database /tmp/backup -incremental=93222
Incremental Restore
orientdb> create database remote:localhost/mydb root root plocal graph -
restore=/tmp/backup
Creating database [remote:localhost/mydb] using the storage type [plocal]...
Connecting to database [remote:localhost/mydb] with user 'admin'...OK
Database created successfully.
Current database is: remote:localhost/mydb
For more information look at: http://orientdb.com/docs/last/Incremental-Backup-And-Restore.html.
Non-Stop Incremental Backup

Confidential
Incremental Backup - Studio
Retention days are the
number of days you
want to keep the backup
files on your hard drive

Confidential
You can restore a backup with
just one click

Confidential

Confidential
Security - OSystem
• OSystem is the server’s database
• Server Users can be managed using this database
• Contains Auditing Logs
• Contains Backup/Restore Event Logs
• In the future, it will contain Metrics too

Confidential
Security - Password Hashing
• PBKDF2 HASH algorithm with a 24-bit length
SALT per user for a configurable number of
iterations
• Used for database and server users
<user name=“root"
password=“{PBKDF2WithHmacSHA256}2BC91B997B:3CBB55E954C48B771A6B5D2FDD8D7:65536”
resources="*"/>
SALT = 65536 by
default
{ALGORITHM} as prefix ensures
back compatibility with previous
OrientDB versions

Confidential
Security - Encryption at REST
orientdb> CONFIG SET storage.encryptionKey T1JJRU5UREJfSVNfQ09PTA==
orientdb> CREATE DATABASE plocal:/tmp/db/encrypted-db admin admin
plocal document -encryption=aes
Create an encrypted database
Encrypt only one cluster
orientdb> ALTER CLUSTER Salary encryption aes
Open an encrypted database
orientdb> CONFIG SET storage.encryptionKey T1JJRU5UREJfSVNfQ09PTA==
orientdb> CONNECT plocal:/tmp/db/encrypted-db admin admin

Confidential
Security - Password Validator
Password Validator is pluggable.
Register your own
implementation in security.json
file
The password validator in the
bundle is flexible enough for
most use cases

Confidential
Security - Authenticator
Authenticators are
executed in chain, so
the order matters
Authenticators are pluggable.
Register your own implementation
in security.json file

Confidential
Security - Kerberos Support
Support for Kerberos authentication and
full browser SPNEGO support. See the
security configuration page for full details
on configuring this authenticator for
Kerberos.

Confidential
Sends auditing logs to the SysLog daemon.
Add this in config/orientdb-server-config.xml file:

<handler class="com.orientechnologies.security.syslog.ODefaultSyslog">
<parameters>
<parameter name="enabled" value="true"/>
<parameter name="debug" value="false"/>
<parameter name="hostname" value="localhost"/>
<parameter name="port" value="514"/>
<parameter name="appName" value="OrientDB"/>
</parameters>
</handler>
For more information look at: http://orientdb.com/docs/last/SysLog-Plugin.html
Security - SysLog

Confidential
Distributed - Easier Configuration
Support for elastic configuration computed at run-time:
writeQuorum: “majority” = N/2+1
writeQuorum: “all” = all nodes
Static node ownership configuration:
"client_usa": {
"owner": "usa",
"servers" : [ "usa", "europe", "asia" ]
}

Confidential
Distributed - Changed Transport
B
A
C
No more Hazelcast Queues.
Now there’s a direct
connection via the OrientDB
Binary Protocol
From 3x to 10x faster with just 3
nodes. With 10 nodes, it’s even
100x faster!

Confidential
Distributed - Multi-Thread Execution
A
Parallel execution with the
operations ordering guaranteed

Confidential
Distributed - Delta Synchronisation
B
A
C
Only the delta is
sent to the server
Server Restart takes
only a few seconds
now!
Server C
is restarted

Confidential
Distributed - Replica Server
B
A
C
writeQuorum: “majority”
R1 R5R4R3R2
Master Servers = 3
Replica Servers = 5
Only Master
Servers concur in
the writeQuorum
…

Confidential
Distributed - Load Balancing
B
A
C …
Client
Strategies:
• STICKY (default)
• ROUND_ROBIN_CONNECT
• ROUND_ROBIN_REQUEST

Confidential
Distributed - Improved Output
2016-06-01 16:19:10:363 INFO [asia] New distributed configuration for database: GratefulDeadConcerts (version=44)
LEGEND: X = Owner, o = Copy
+-------------+-----------+----------+------+------+------+
| | | |MASTER|MASTER|MASTER|
| | | |ONLINE|ONLINE|ONLINE|
+-------------+-----------+----------+------+------+------+
|CLUSTER |writeQuorum|readQuorum| usa |europe| asia |
+-------------+-----------+----------+------+------+------+
|* | 2 | 1 | X | o | o |
|e_2 | 2 | 1 | o | o | X |
|e_7 | 2 | 1 | o | X | o |
|followed_by_1| 2 | 1 | o | X | o |
|followed_by_2| 2 | 1 | o | X | o |
|internal | 2 | 1 | | | |
|ofunction_0 | 2 | 1 | o | X | o |
|ofunction_1 | 2 | 1 | o | o | X |
|orole_0 | 2 | 1 | o | X | o |
|orole_1 | 2 | 1 | o | o | X |
|oschedule_0 | 2 | 1 | o | X | o |
|osequence_1 | 2 | 1 | o | o | X |
|ouser_0 | 2 | 1 | o | X | o |
|ouser_1 | 2 | 1 | o | o | X |
|sung_by | 2 | 1 | o | X | o |
|sung_by_6 | 2 | 1 | o | o | X |
|v_3 | 2 | 1 | o | X | o |
|v_7 | 2 | 1 | o | o | X |
|written_by | 2 | 1 | o | X | o |
|written_by_7 | 2 | 1 | o | X | o |
+-------------+-----------+----------+------+------+------+
It’s much easier to understand
which server owns which cluster

Confidential
Distributed - New SQL Commands
Remove a server from the configuration
HA REMOVE SERVER <server-name>
Force the resynchronisation of the entire database
HA SYNC DATABASE
Force the resynchronisation of one cluster
HA SYNC CLUSTER <cluster-name>

Confidential
Teleporter
*Officially supported RDBMS:
Oracle, Microsoft SQLServer, MySQL and Postgres

Confidential
Teleporter First Results
First 5 users’ feedback by importing from an Oracle DBMS
to OrientDB using Teleporter:
• Importing setup took less than 5 minutes
• Importing of databases of 5 Million records from Oracle
took about 30 minutes
• Zero or Minor changes in queries
• up to 10x increase in performance with simple queries
(lookup on index and one JOIN)
• up to 100x with complex traversal with +4 JOINs

Confidential
Integration is the Key
OrientDB
ETL
Teleporter
JDBC Driver
OrientDB can have a partial or
complete copy of a RDBMS
database.
BI tools designed for RDBMS work
on OrientDB too.

Confidential
Enterprise Differentiation
Core Features
(Embedded, HA, Sharding, Replication,
Console and GUI)
Enterprise Features
(Profiler, Incremental Backup, Auditing,
Kerberos, Security and Encryption)
Support
(Product Support, Emergency Patches
and Consultative Support)
Additional Tools
(Ops Manager and Teleporter)
Community Enterprise
License
Open Source Apache 2
Commercial

Confidential
Roadmap OrientDB v3.0 (Q4 2016)
• Improve In-Memory Layout (mechanical-sympathy friendly)
• 2x-5x Compression of Data on Disk and RAM
• Improve Cross Data-Center Replication
• Improve Teleporter to Import Automatically from Neo4j and
MongoDB
• Automatic Sharding (DHT + Pregel traversal)
• TinkerPop Standard v3.0 support
• New SQL Engine for faster Parallel and Distributed execution

Confidential
Getting Started Course

Thank you!
@orientdb
OrientDB is a registered trademark by OrientDB LTD,
all the other trademarks mentioned in this presentation are owned by their legit owners.
Q&A
For more information, look at:
http://orientdb.com/docs/last/Release-2.2.0.html

Presentation of OrientDB v2.2 - Webinar

Recommended

Recommended

More Related Content

What's hot

What's hot (20)

Viewers also liked

Viewers also liked (20)

Similar to Presentation of OrientDB v2.2 - Webinar

Similar to Presentation of OrientDB v2.2 - Webinar (20)

Recently uploaded

Recently uploaded (20)

Presentation of OrientDB v2.2 - Webinar