www.arangodb.com
Polyglot Persistence
&
Multi-Model Databases
Michael Hackstein
@mchacki
Java User Group Hessen
Michael Hackstein
‣ ArangoDB Core Team
‣ Web Frontend
‣ Graph visualisation
‣ Graph features
‣ Host of cologne.js
‣ Master’s Degree

(spec. Databases and

Information Systems)
2
The Single Model era is over
3
Relational World
The Multi Model era begins
4
NoSQL World
Documents - JSON
Graphs
Key Value
{
“type“: "pants",
“waist": 32,
“length”: 34,
“color": "blue",
“material”: “cotton"
}
{
“type“: "television",
“diagonal screen size": 46,
“hdmi inputs": 3,
“wall mountable": true,
“built-in digital tuner": true,
“dynamic contrast ratio”: “50,000:1”,
Resolution”: “1920x1080”
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
The Multi Model era begins
4
NoSQL World
Documents - JSON
Graphs
Key Value
{
“type“: "pants",
“waist": 32,
“length”: 34,
“color": "blue",
“material”: “cotton"
}
{
“type“: "television",
“diagonal screen size": 46,
“hdmi inputs": 3,
“wall mountable": true,
“built-in digital tuner": true,
“dynamic contrast ratio”: “50,000:1”,
Resolution”: “1920x1080”
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
‣ Normally based on key-value stores (each document still
has a unique key)
‣ Allow to save documents with logical similarity in
“collections”
‣ Treat data records as attribute-structured documents
(data is no more opaque)
‣ Often allow querying and indexing document attributes
The Multi Model era begins
4
NoSQL World
Documents - JSON
Graphs
Key Value
{
“type“: "pants",
“waist": 32,
“length”: 34,
“color": "blue",
“material”: “cotton"
}
{
“type“: "television",
“diagonal screen size": 46,
“hdmi inputs": 3,
“wall mountable": true,
“built-in digital tuner": true,
“dynamic contrast ratio”: “50,000:1”,
Resolution”: “1920x1080”
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
‣ Focussed on m-to-n relations between entities
‣ Stores property graphs: entities and edges can have
attributes
‣ Easily query paths of variable length
‣ Normally based on key-value stores (each document still
has a unique key)
‣ Allow to save documents with logical similarity in
“collections”
‣ Treat data records as attribute-structured documents
(data is no more opaque)
‣ Often allow querying and indexing document attributes
The Multi Model era begins
4
NoSQL World
Documents - JSON
Graphs
Key Value
{
“type“: "pants",
“waist": 32,
“length”: 34,
“color": "blue",
“material”: “cotton"
}
{
“type“: "television",
“diagonal screen size": 46,
“hdmi inputs": 3,
“wall mountable": true,
“built-in digital tuner": true,
“dynamic contrast ratio”: “50,000:1”,
Resolution”: “1920x1080”
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
‣ Map value data to unique string keys (identifiers)
‣ Treat data as opaque (data has no schema)
‣ Can implement scaling and partitioning easily
‣ Focussed on m-to-n relations between entities
‣ Stores property graphs: entities and edges can have
attributes
‣ Easily query paths of variable length
‣ Normally based on key-value stores (each document still
has a unique key)
‣ Allow to save documents with logical similarity in
“collections”
‣ Treat data records as attribute-structured documents
(data is no more opaque)
‣ Often allow querying and indexing document attributes
e-commerce system in Relational World
5
Sales-History
Shopping-Cart
Recommendations Customer
Product-Catalog
Polyglot Persistence
6
Source: Martin Fowler, http://martinfowler.com/articles/nosql-intro.pdf
Reporting
RDBMS
Product Catalog
MongoDB
Shopping Cart
Riak
User activity log
Cassandra
Analytics
Cassandra
Recommendations
Neo4J
Financial Data
RDBMS
User Sessions
Redis
Polyglot Persistence
6
Source: Martin Fowler, http://martinfowler.com/articles/nosql-intro.pdf
Reporting
RDBMS
Product Catalog
MongoDB
Shopping Cart
Riak
User activity log
Cassandra
Analytics
Cassandra
Recommendations
Neo4J
Financial Data
RDBMS
User Sessions
Redis
Shopping Cart
KeyValue
Reporting
RDBMS
Product Catalog
Document
User activity log
Column
Analytics
Column
Recommendations
Graph
Financial Data
RDBMS
User Sessions
KeyValue
Single Model Databases
7
Recommendations
Product-CatalogShopping-Cart
Sales-History Customer
{
“userID": 239178239,
“productID”: 128623883,
“number": 5,
“price”: 12.20,
}
{
“userID": 239178239,
“productID”: 128623883,
“number": 5,
“price”: 12.20,
}
{
“Name": "Smith",
“lastLogin”: “2012-11-01",
“Visits": 121,
“shipping address”: “abc”,
“shipping address”: “def”
}
{
“Name": "Meyer",
“lastLogin”: “2012-11-21",
“Visits": 20,
“shipping address”: “xyz”,
}
423453453
4328, “shirt”, “L”, 1, 12.99
6378, “sweater”, “M”, 2, 37.95
3245, “sweater”, “blue”, 1, 99.95
3245, “pants”, “32/34”, “black”, 1, 99.95
=>
874365563
5463, “shirt”, “S”, 1, 9.99
6378, “sweater”, “M”, 2, 37.95
3245, “pants”, “32/34”, “black”, 1, 99.95
=>
{
“type“: "pants",
“waist": 32,
“length”: 34,
“color": "blue",
“material”: “cotton"
}
{
“type“: "television",
“diagonal screen size": 46,
“hdmi inputs": 3,
“wall mountable": true,
“built-in digital tuner": true,
“dynamic contrast ratio”: “50,000:1”,
Resolution”: “1920x1080”
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
Single Model Databases
7
Recommendations
Product-CatalogShopping-Cart
Sales-History Customer
{
“userID": 239178239,
“productID”: 128623883,
“number": 5,
“price”: 12.20,
}
{
“userID": 239178239,
“productID”: 128623883,
“number": 5,
“price”: 12.20,
}
{
“Name": "Smith",
“lastLogin”: “2012-11-01",
“Visits": 121,
“shipping address”: “abc”,
“shipping address”: “def”
}
{
“Name": "Meyer",
“lastLogin”: “2012-11-21",
“Visits": 20,
“shipping address”: “xyz”,
}
423453453
4328, “shirt”, “L”, 1, 12.99
6378, “sweater”, “M”, 2, 37.95
3245, “sweater”, “blue”, 1, 99.95
3245, “pants”, “32/34”, “black”, 1, 99.95
=>
874365563
5463, “shirt”, “S”, 1, 9.99
6378, “sweater”, “M”, 2, 37.95
3245, “pants”, “32/34”, “black”, 1, 99.95
=>
{
“type“: "pants",
“waist": 32,
“length”: 34,
“color": "blue",
“material”: “cotton"
}
{
“type“: "television",
“diagonal screen size": 46,
“hdmi inputs": 3,
“wall mountable": true,
“built-in digital tuner": true,
“dynamic contrast ratio”: “50,000:1”,
Resolution”: “1920x1080”
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
DocumentStore GraphStore DocumentStore
DocumentStoreKeyValueStore
Single Model Databases
7
Recommendations
Product-CatalogShopping-Cart
Sales-History Customer
{
“userID": 239178239,
“productID”: 128623883,
“number": 5,
“price”: 12.20,
}
{
“userID": 239178239,
“productID”: 128623883,
“number": 5,
“price”: 12.20,
}
{
“Name": "Smith",
“lastLogin”: “2012-11-01",
“Visits": 121,
“shipping address”: “abc”,
“shipping address”: “def”
}
{
“Name": "Meyer",
“lastLogin”: “2012-11-21",
“Visits": 20,
“shipping address”: “xyz”,
}
423453453
4328, “shirt”, “L”, 1, 12.99
6378, “sweater”, “M”, 2, 37.95
3245, “sweater”, “blue”, 1, 99.95
3245, “pants”, “32/34”, “black”, 1, 99.95
=>
874365563
5463, “shirt”, “S”, 1, 9.99
6378, “sweater”, “M”, 2, 37.95
3245, “pants”, “32/34”, “black”, 1, 99.95
=>
{
“type“: "pants",
“waist": 32,
“length”: 34,
“color": "blue",
“material”: “cotton"
}
{
“type“: "television",
“diagonal screen size": 46,
“hdmi inputs": 3,
“wall mountable": true,
“built-in digital tuner": true,
“dynamic contrast ratio”: “50,000:1”,
Resolution”: “1920x1080”
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
DocumentStore GraphStore DocumentStore
DocumentStoreKeyValueStore
Benefits
‣ Natural mapping of data into DB
‣ DB optimized for the data format
‣ Queries are tailored for your
data format
‣ Focus on writing business logic
8
‣ Data has to be stored
redundantly and has to be kept
in sync
‣ Several technologies involved
‣ Administration effort is huge
Overhead&
Solution: Multi Model Database
‣ Can natively store several kinds of data models:
‣ Key-value pairs
‣ Documents
‣ Graphs
‣ Delivers query mechanisms for all data models
9
Polyglot Persistence Revisited
10
Source: Martin Fowler, http://martinfowler.com/articles/nosql-intro.pdf
Shopping Cart
KeyValue
Reporting
RDBMS
Product Catalog
Document
User activity log
Column
Analytics
Column
Recommendations
Graph
Financial Data
RDBMS
User Sessions
KeyValue
Polyglot Persistence Revisited
10
Source: Martin Fowler, http://martinfowler.com/articles/nosql-intro.pdf
Shopping Cart
KeyValue
Reporting
RDBMS
Product Catalog
Document
User activity log
Column
Analytics
Column
Recommendations
Graph
Financial Data
RDBMS
User Sessions
KeyValue
Reporting
RDBMS
Product Catalog
ArangoDB
Shopping Cart
ArangoDB
User activity log
Cassandra
Analytics
Cassandra
Recommendations
ArangoDB
Financial Data
ArangoDB
User Sessions
ArangoDB
Use Case: Multi-Model-Databases
11
Recommendations
Product-CatalogShopping-Cart
Sales-History Customer
{
“userID": 239178239,
“productID”: 128623883,
“number": 5,
“price”: 12.20,
}
{
“userID": 239178239,
“productID”: 128623883,
“number": 5,
“price”: 12.20,
}
{
“Name": "Smith",
“lastLogin”: “2012-11-01",
“Visits": 121,
“shipping address”: “abc”,
“shipping address”: “def”
}
{
“Name": "Meyer",
“lastLogin”: “2012-11-21",
“Visits": 20,
“shipping address”: “xyz”,
}
423453453
4328, “shirt”, “L”, 1, 12.99
6378, “sweater”, “M”, 2, 37.95
3245, “sweater”, “blue”, 1, 99.95
3245, “pants”, “32/34”, “black”, 1, 99.95
=>
874365563
5463, “shirt”, “S”, 1, 9.99
6378, “sweater”, “M”, 2, 37.95
3245, “pants”, “32/34”, “black”, 1, 99.95
=>
{
“type“: "pants",
“waist": 32,
“length”: 34,
“color": "blue",
“material”: “cotton"
}
{
“type“: "television",
“diagonal screen size": 46,
“hdmi inputs": 3,
“wall mountable": true,
“built-in digital tuner": true,
“dynamic contrast ratio”: “50,000:1”,
Resolution”: “1920x1080”
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
Use Case: Multi-Model-Databases
11
Recommendations
Product-CatalogShopping-Cart
Sales-History Customer
{
“userID": 239178239,
“productID”: 128623883,
“number": 5,
“price”: 12.20,
}
{
“userID": 239178239,
“productID”: 128623883,
“number": 5,
“price”: 12.20,
}
{
“Name": "Smith",
“lastLogin”: “2012-11-01",
“Visits": 121,
“shipping address”: “abc”,
“shipping address”: “def”
}
{
“Name": "Meyer",
“lastLogin”: “2012-11-21",
“Visits": 20,
“shipping address”: “xyz”,
}
423453453
4328, “shirt”, “L”, 1, 12.99
6378, “sweater”, “M”, 2, 37.95
3245, “sweater”, “blue”, 1, 99.95
3245, “pants”, “32/34”, “black”, 1, 99.95
=>
874365563
5463, “shirt”, “S”, 1, 9.99
6378, “sweater”, “M”, 2, 37.95
3245, “pants”, “32/34”, “black”, 1, 99.95
=>
{
“type“: "pants",
“waist": 32,
“length”: 34,
“color": "blue",
“material”: “cotton"
}
{
“type“: "television",
“diagonal screen size": 46,
“hdmi inputs": 3,
“wall mountable": true,
“built-in digital tuner": true,
“dynamic contrast ratio”: “50,000:1”,
Resolution”: “1920x1080”
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
DocumentStore GraphStore DocumentStore
DocumentStoreKeyValueStore
Use Case: Multi-Model-Databases
11
Recommendations
Product-CatalogShopping-Cart
Sales-History Customer
{
“userID": 239178239,
“productID”: 128623883,
“number": 5,
“price”: 12.20,
}
{
“userID": 239178239,
“productID”: 128623883,
“number": 5,
“price”: 12.20,
}
{
“Name": "Smith",
“lastLogin”: “2012-11-01",
“Visits": 121,
“shipping address”: “abc”,
“shipping address”: “def”
}
{
“Name": "Meyer",
“lastLogin”: “2012-11-21",
“Visits": 20,
“shipping address”: “xyz”,
}
423453453
4328, “shirt”, “L”, 1, 12.99
6378, “sweater”, “M”, 2, 37.95
3245, “sweater”, “blue”, 1, 99.95
3245, “pants”, “32/34”, “black”, 1, 99.95
=>
874365563
5463, “shirt”, “S”, 1, 9.99
6378, “sweater”, “M”, 2, 37.95
3245, “pants”, “32/34”, “black”, 1, 99.95
=>
{
“type“: "pants",
“waist": 32,
“length”: 34,
“color": "blue",
“material”: “cotton"
}
{
“type“: "television",
“diagonal screen size": 46,
“hdmi inputs": 3,
“wall mountable": true,
“built-in digital tuner": true,
“dynamic contrast ratio”: “50,000:1”,
Resolution”: “1920x1080”
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
{
“type": "sweater",
“color": "blue",
“size": “M”,
“material”: “wool”,
“form”: “turtleneck"
}
DocumentStore GraphStore DocumentStore
DocumentStoreKeyValueStore
My four favorite features of
‣ AQL offering joins & traversals
‣ ACID including Multi Collection Transactions
‣ MULTI-MODEL stores graphs and documents
12
My four favorite features of
‣ AQL offering joins & traversals
‣ ACID including Multi Collection Transactions
‣ MULTI-MODEL stores graphs and documents
12
‣ FOXX extend the API and adapt it to your needs
AQL
13
FOR user IN users
RETURN user
AQL
14
FOR user IN users
FILTER user.name == "alice"
RETURN user
AQL
15
FOR user IN users
FILTER user.name == "alice"
FOR invoice IN invoices
FILTER user._key == invoice.customer
RETURN {
user: user,
invoice: invoice
}
AQL
16
FOR user IN users
FILTER user.name == "alice"
RETURN {
user: user,
invoices: (
FOR invoice IN invoices
FILTER user._key == invoice.customer
RETURN invoice
)
}
AQL
17
FOR user IN users
FILTER user.name == "alice"
RETURN {
user: user,
hasToPay: SUM(
FOR invoice IN invoices
FILTER user._key == invoice.customer
FILTER !invoice.payed
RETURN invoice.price
)
}
AQL - Alternative
18
FOR user IN users
FILTER user.name == "alice"
FOR invoice IN invoices
FILTER user._key == invoice.customer
FILTER !invoice.payed
COLLECT u = user AGGREGATE toPay = SUM(invoice.price)
RETURN {
user: u,
hasToPay: toPay
}
AQL
19
FOR user IN users
FILTER user.name == "alice"
FOR product IN OUTBOUND user has_bought
RETURN product
AQL
20
FOR user IN users
FILTER user.name == "alice"
FOR product IN OUTBOUND user has_bought
LIMIT 10
RETURN product
AQL
21
FOR user IN users
FILTER user.name == "alice"
FOR product, action IN OUTBOUND user has_bought
SORT action.timestamp DESC
LIMIT 10
RETURN product
AQL
22
FOR user IN users
FILTER user.name == "alice"
FOR recommendation IN 3 ANY user has_bought
OPTIONS { bfs: true, uniqueVertices: "global" }
LIMIT 10
RETURN recommendation
AQL
23
FOR user IN users
FILTER user.name == "alice"
FOR recommendation, action, path IN 3 ANY user has_bought
FILTER path.vertices[2].age <= user.age + 5
AND path.vertices[2].age >= user.age - 5
LIMIT 10
RETURN recommendation
AQL
24
FOR user IN users
FILTER user.name == "alice"
FOR recommendation, action, path IN 3 ANY user has_bought
FILTER path.vertices[2].age <= user.age + 5
AND path.vertices[2].age >= user.age - 5
FILTER recommendation.price < 25
LIMIT 10
RETURN recommendation
ACID - Transactions
‣ Invoke a transaction:
db._executeTransaction({
collections: {
write: ["users", "products"],
read: "has_bought"
},
action: function() {
// all operations go here
}
});
25
ACID - Transactions
‣ Invoke a transaction:
db._executeTransaction({
collections: {
write: ["users", "products"],
read: "has_bought"
},
action: function() {
// all operations go here
}
});
25
throw "failure"; // Triggers rollback
‣ Native mapping of data into DB
‣ DB optimized
‣ Queries are tailored for your
data format
‣ Focus on writing business logic
26
‣ Data has to be stored
redundantly and has to be kept
in sync
‣ Several technologies involved
‣ Administration effort is huge
Benefits Overhead&
‣ Native mapping of data into DB
‣ DB optimized
‣ Queries are tailored for your
data format
‣ Focus on writing business logic
26
‣ One technology involved
Benefits Overhead&
Benchmark Comparison
Source: https://www.arangodb.com/2015/10/benchmark-postgresql-mongodb-arangodb/
Foxx
‣ Add your own customized and versioned REST-API on top of
ArangoDB in JavaScript
‣ Include as a microservice in Rails, Node.js etc.
‣ Ship an administration fronted with it
‣ Built-in authentication using OAuth2.0 or HTTP-Basic Auth
‣ Operations are encapsulated in the database
‣ low network traffic, direct data access
‣ increases data privacy
➡ Multi-device setups
➡ Microservice Architectures
/
(~(
) ) /_/
( _-----_(@ @)
(  /
/|/--| V
" " " "
28
Foxx Example
29
router.get("/recommend/:price", function(req, res) {
res.json(db._query(
});
{
maxPrice: req.params("price"),
name: req.session.username
}).toArray());
`FOR user IN users
FILTER user.name == @name
FOR recommendation, action, path IN 3 ANY user has_bought
OPTIONS { bfs: true, uniqueVertices: "global" }
FILTER path.vertices[2].age <= user.age + 5
AND path.vertices[2].age >= user.age - 5
FILTER recommendation.price < @maxPrice
LIMIT 10
RETURN recommendation`,
Does it Scale?
‣ Sharding (Huge Dataset, Write-Scaling)
‣ Collection: distributed across several servers
‣ Distributed by: List of Attributes (default: _key)
‣ Number of Shards immutable
‣ Has to be defined on creation
‣ Can be different for all collections
‣ Suggested: #Servers
30
2
Does it Scale?
‣ Sharding (Huge Dataset, Write-Scaling)
‣ Collection: distributed across several servers
‣ Distributed by: List of Attributes (default: _key)
‣ Number of Shards immutable
‣ Has to be defined on creation
‣ Can be different for all collections
‣ Suggested: #Servers
30
2
‣ Replication (Failover, Read-Scaling)
‣ Shard: can have n Followers (Replicas)
‣ Followers:
‣ do not accept writes
‣ synchronous (identical data)
‣ placed on different machine (if possible)
Speaking of Clusters ...
31
32
33
Marathon
‣ Connects the cluster
‣ Ressource management
‣ Knows which servers are online
‣ Knows which resources they have
34
Marathon
‣ Builds on top of Mesos
‣ Application Monitor
‣ Can start new applications
‣ "Monitors" running applications
‣ If a machine/process dies Marathon restarts it
‣ Can stop applications
➡ Can scale up / down running applications within a cluster
‣ Offers available resources to new applications
‣ If Marathon dies it is restarted somewhere else
35
‣ Builds on top of Marathon
‣ "Data-Center-Operating-System"
‣ Offers one-click installers for applications (DC/OS Universe)
‣ Includes Service Discovery
‣ Includes Reverse Proxying
➡ You just run an Application through DC/OS and you can
communicate with it without ever knowing any IP address
36
Frameworks
‣ Marathons little helpers
‣ Know details about complete Applications
‣ Communicate with Marathon to order sub-processes
‣ Can describe additional conditions for processes
‣ Like: "Do not run all DB instances on the same Machine"
‣ Can trigger marathon to scale up/down processes
➡ ArangoDB has a Marathon Framework
37
Live Demo
ArangoDB on DC/OS
38
Is Mesosphere required?
‣ ArangoDB can run clusters without it
‣ Setup Requires manual effort (can be scripted):
‣ Configure IP addresses
‣ Correct startup ordering
‣ This works:
‣ Automatic Failover (Follower takes over if leader dies)
‣ Rebalancing of shards
‣ Everything inside of ArangoDB
‣ This is based on Mesos:
‣ Complete self healing
‣ Automatic restart of ArangoDBs (on new machines)
➡We suggest you have someone on call
39
Does your data-model scale?
‣ Rule of thumb: "The more complex the query, the less it
scales".
‣ Indexed-Attribute lookups:
‣ Scale "infinitely"
‣ Examples
‣ Key/Value
‣ FOR doc IN sharded FILTER doc.name == 'Michael'
‣ Joins:
‣ Each join operation requires one additional round-trip (find left side, than
find right side)
‣ Scale "okayish"
‣ Graphs:
‣ Each search depth potentially requires 2 join-like operations
‣ A single-server needs to hold a large intermediate result
‣ Does not scale too good
40
‣ open source and free (Apache 2 license)
‣ sharding & replication
‣ JavaScript throughout (V8 built into server)
‣ drivers for a wide range of languages
‣ web frontend
‣ good & complete documentation
‣ professional as well as community support
41
An overview of other features
What about Java?
‣ Basic Driver developed in-house
‣ Tutorial: https://www.arangodb.com/tutorials/tutorial-java/
‣ We are working on a Spring-Data integration
‣ We are very happy to get input on this
‣ Feedback
‣ Feature Requests
‣ Personal Opinion on other Drivers/Integration you worked with
‣ Development
42
Join our growing community
43
.. working on the geo index, the full text search and
many APIs: Ruby, Python, PHP, Java, D,
Javascript, ...
Thank you
‣ Further questions?
‣ Follow us on twitter: @arangodb
‣ Join or community slack: arangodb-community.slack.com
‣ Join or google group: https://groups.google.com/forum/#!forum/arangodb
‣ Follow me on twitter/github: @mchacki
‣ Write me a mail: michael@arangodb.com
44

Polyglot Persistence & Multi-Model Databases

  • 1.
  • 2.
    Michael Hackstein ‣ ArangoDBCore Team ‣ Web Frontend ‣ Graph visualisation ‣ Graph features ‣ Host of cologne.js ‣ Master’s Degree
 (spec. Databases and
 Information Systems) 2
  • 3.
    The Single Modelera is over 3 Relational World
  • 4.
    The Multi Modelera begins 4 NoSQL World Documents - JSON Graphs Key Value { “type“: "pants", “waist": 32, “length”: 34, “color": "blue", “material”: “cotton" } { “type“: "television", “diagonal screen size": 46, “hdmi inputs": 3, “wall mountable": true, “built-in digital tuner": true, “dynamic contrast ratio”: “50,000:1”, Resolution”: “1920x1080” } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" }
  • 5.
    The Multi Modelera begins 4 NoSQL World Documents - JSON Graphs Key Value { “type“: "pants", “waist": 32, “length”: 34, “color": "blue", “material”: “cotton" } { “type“: "television", “diagonal screen size": 46, “hdmi inputs": 3, “wall mountable": true, “built-in digital tuner": true, “dynamic contrast ratio”: “50,000:1”, Resolution”: “1920x1080” } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" } ‣ Normally based on key-value stores (each document still has a unique key) ‣ Allow to save documents with logical similarity in “collections” ‣ Treat data records as attribute-structured documents (data is no more opaque) ‣ Often allow querying and indexing document attributes
  • 6.
    The Multi Modelera begins 4 NoSQL World Documents - JSON Graphs Key Value { “type“: "pants", “waist": 32, “length”: 34, “color": "blue", “material”: “cotton" } { “type“: "television", “diagonal screen size": 46, “hdmi inputs": 3, “wall mountable": true, “built-in digital tuner": true, “dynamic contrast ratio”: “50,000:1”, Resolution”: “1920x1080” } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" } ‣ Focussed on m-to-n relations between entities ‣ Stores property graphs: entities and edges can have attributes ‣ Easily query paths of variable length ‣ Normally based on key-value stores (each document still has a unique key) ‣ Allow to save documents with logical similarity in “collections” ‣ Treat data records as attribute-structured documents (data is no more opaque) ‣ Often allow querying and indexing document attributes
  • 7.
    The Multi Modelera begins 4 NoSQL World Documents - JSON Graphs Key Value { “type“: "pants", “waist": 32, “length”: 34, “color": "blue", “material”: “cotton" } { “type“: "television", “diagonal screen size": 46, “hdmi inputs": 3, “wall mountable": true, “built-in digital tuner": true, “dynamic contrast ratio”: “50,000:1”, Resolution”: “1920x1080” } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" } ‣ Map value data to unique string keys (identifiers) ‣ Treat data as opaque (data has no schema) ‣ Can implement scaling and partitioning easily ‣ Focussed on m-to-n relations between entities ‣ Stores property graphs: entities and edges can have attributes ‣ Easily query paths of variable length ‣ Normally based on key-value stores (each document still has a unique key) ‣ Allow to save documents with logical similarity in “collections” ‣ Treat data records as attribute-structured documents (data is no more opaque) ‣ Often allow querying and indexing document attributes
  • 8.
    e-commerce system inRelational World 5 Sales-History Shopping-Cart Recommendations Customer Product-Catalog
  • 9.
    Polyglot Persistence 6 Source: MartinFowler, http://martinfowler.com/articles/nosql-intro.pdf Reporting RDBMS Product Catalog MongoDB Shopping Cart Riak User activity log Cassandra Analytics Cassandra Recommendations Neo4J Financial Data RDBMS User Sessions Redis
  • 10.
    Polyglot Persistence 6 Source: MartinFowler, http://martinfowler.com/articles/nosql-intro.pdf Reporting RDBMS Product Catalog MongoDB Shopping Cart Riak User activity log Cassandra Analytics Cassandra Recommendations Neo4J Financial Data RDBMS User Sessions Redis Shopping Cart KeyValue Reporting RDBMS Product Catalog Document User activity log Column Analytics Column Recommendations Graph Financial Data RDBMS User Sessions KeyValue
  • 11.
    Single Model Databases 7 Recommendations Product-CatalogShopping-Cart Sales-HistoryCustomer { “userID": 239178239, “productID”: 128623883, “number": 5, “price”: 12.20, } { “userID": 239178239, “productID”: 128623883, “number": 5, “price”: 12.20, } { “Name": "Smith", “lastLogin”: “2012-11-01", “Visits": 121, “shipping address”: “abc”, “shipping address”: “def” } { “Name": "Meyer", “lastLogin”: “2012-11-21", “Visits": 20, “shipping address”: “xyz”, } 423453453 4328, “shirt”, “L”, 1, 12.99 6378, “sweater”, “M”, 2, 37.95 3245, “sweater”, “blue”, 1, 99.95 3245, “pants”, “32/34”, “black”, 1, 99.95 => 874365563 5463, “shirt”, “S”, 1, 9.99 6378, “sweater”, “M”, 2, 37.95 3245, “pants”, “32/34”, “black”, 1, 99.95 => { “type“: "pants", “waist": 32, “length”: 34, “color": "blue", “material”: “cotton" } { “type“: "television", “diagonal screen size": 46, “hdmi inputs": 3, “wall mountable": true, “built-in digital tuner": true, “dynamic contrast ratio”: “50,000:1”, Resolution”: “1920x1080” } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" }
  • 12.
    Single Model Databases 7 Recommendations Product-CatalogShopping-Cart Sales-HistoryCustomer { “userID": 239178239, “productID”: 128623883, “number": 5, “price”: 12.20, } { “userID": 239178239, “productID”: 128623883, “number": 5, “price”: 12.20, } { “Name": "Smith", “lastLogin”: “2012-11-01", “Visits": 121, “shipping address”: “abc”, “shipping address”: “def” } { “Name": "Meyer", “lastLogin”: “2012-11-21", “Visits": 20, “shipping address”: “xyz”, } 423453453 4328, “shirt”, “L”, 1, 12.99 6378, “sweater”, “M”, 2, 37.95 3245, “sweater”, “blue”, 1, 99.95 3245, “pants”, “32/34”, “black”, 1, 99.95 => 874365563 5463, “shirt”, “S”, 1, 9.99 6378, “sweater”, “M”, 2, 37.95 3245, “pants”, “32/34”, “black”, 1, 99.95 => { “type“: "pants", “waist": 32, “length”: 34, “color": "blue", “material”: “cotton" } { “type“: "television", “diagonal screen size": 46, “hdmi inputs": 3, “wall mountable": true, “built-in digital tuner": true, “dynamic contrast ratio”: “50,000:1”, Resolution”: “1920x1080” } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" } DocumentStore GraphStore DocumentStore DocumentStoreKeyValueStore
  • 13.
    Single Model Databases 7 Recommendations Product-CatalogShopping-Cart Sales-HistoryCustomer { “userID": 239178239, “productID”: 128623883, “number": 5, “price”: 12.20, } { “userID": 239178239, “productID”: 128623883, “number": 5, “price”: 12.20, } { “Name": "Smith", “lastLogin”: “2012-11-01", “Visits": 121, “shipping address”: “abc”, “shipping address”: “def” } { “Name": "Meyer", “lastLogin”: “2012-11-21", “Visits": 20, “shipping address”: “xyz”, } 423453453 4328, “shirt”, “L”, 1, 12.99 6378, “sweater”, “M”, 2, 37.95 3245, “sweater”, “blue”, 1, 99.95 3245, “pants”, “32/34”, “black”, 1, 99.95 => 874365563 5463, “shirt”, “S”, 1, 9.99 6378, “sweater”, “M”, 2, 37.95 3245, “pants”, “32/34”, “black”, 1, 99.95 => { “type“: "pants", “waist": 32, “length”: 34, “color": "blue", “material”: “cotton" } { “type“: "television", “diagonal screen size": 46, “hdmi inputs": 3, “wall mountable": true, “built-in digital tuner": true, “dynamic contrast ratio”: “50,000:1”, Resolution”: “1920x1080” } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" } DocumentStore GraphStore DocumentStore DocumentStoreKeyValueStore
  • 14.
    Benefits ‣ Natural mappingof data into DB ‣ DB optimized for the data format ‣ Queries are tailored for your data format ‣ Focus on writing business logic 8 ‣ Data has to be stored redundantly and has to be kept in sync ‣ Several technologies involved ‣ Administration effort is huge Overhead&
  • 15.
    Solution: Multi ModelDatabase ‣ Can natively store several kinds of data models: ‣ Key-value pairs ‣ Documents ‣ Graphs ‣ Delivers query mechanisms for all data models 9
  • 16.
    Polyglot Persistence Revisited 10 Source:Martin Fowler, http://martinfowler.com/articles/nosql-intro.pdf Shopping Cart KeyValue Reporting RDBMS Product Catalog Document User activity log Column Analytics Column Recommendations Graph Financial Data RDBMS User Sessions KeyValue
  • 17.
    Polyglot Persistence Revisited 10 Source:Martin Fowler, http://martinfowler.com/articles/nosql-intro.pdf Shopping Cart KeyValue Reporting RDBMS Product Catalog Document User activity log Column Analytics Column Recommendations Graph Financial Data RDBMS User Sessions KeyValue Reporting RDBMS Product Catalog ArangoDB Shopping Cart ArangoDB User activity log Cassandra Analytics Cassandra Recommendations ArangoDB Financial Data ArangoDB User Sessions ArangoDB
  • 18.
    Use Case: Multi-Model-Databases 11 Recommendations Product-CatalogShopping-Cart Sales-HistoryCustomer { “userID": 239178239, “productID”: 128623883, “number": 5, “price”: 12.20, } { “userID": 239178239, “productID”: 128623883, “number": 5, “price”: 12.20, } { “Name": "Smith", “lastLogin”: “2012-11-01", “Visits": 121, “shipping address”: “abc”, “shipping address”: “def” } { “Name": "Meyer", “lastLogin”: “2012-11-21", “Visits": 20, “shipping address”: “xyz”, } 423453453 4328, “shirt”, “L”, 1, 12.99 6378, “sweater”, “M”, 2, 37.95 3245, “sweater”, “blue”, 1, 99.95 3245, “pants”, “32/34”, “black”, 1, 99.95 => 874365563 5463, “shirt”, “S”, 1, 9.99 6378, “sweater”, “M”, 2, 37.95 3245, “pants”, “32/34”, “black”, 1, 99.95 => { “type“: "pants", “waist": 32, “length”: 34, “color": "blue", “material”: “cotton" } { “type“: "television", “diagonal screen size": 46, “hdmi inputs": 3, “wall mountable": true, “built-in digital tuner": true, “dynamic contrast ratio”: “50,000:1”, Resolution”: “1920x1080” } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" }
  • 19.
    Use Case: Multi-Model-Databases 11 Recommendations Product-CatalogShopping-Cart Sales-HistoryCustomer { “userID": 239178239, “productID”: 128623883, “number": 5, “price”: 12.20, } { “userID": 239178239, “productID”: 128623883, “number": 5, “price”: 12.20, } { “Name": "Smith", “lastLogin”: “2012-11-01", “Visits": 121, “shipping address”: “abc”, “shipping address”: “def” } { “Name": "Meyer", “lastLogin”: “2012-11-21", “Visits": 20, “shipping address”: “xyz”, } 423453453 4328, “shirt”, “L”, 1, 12.99 6378, “sweater”, “M”, 2, 37.95 3245, “sweater”, “blue”, 1, 99.95 3245, “pants”, “32/34”, “black”, 1, 99.95 => 874365563 5463, “shirt”, “S”, 1, 9.99 6378, “sweater”, “M”, 2, 37.95 3245, “pants”, “32/34”, “black”, 1, 99.95 => { “type“: "pants", “waist": 32, “length”: 34, “color": "blue", “material”: “cotton" } { “type“: "television", “diagonal screen size": 46, “hdmi inputs": 3, “wall mountable": true, “built-in digital tuner": true, “dynamic contrast ratio”: “50,000:1”, Resolution”: “1920x1080” } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" } DocumentStore GraphStore DocumentStore DocumentStoreKeyValueStore
  • 20.
    Use Case: Multi-Model-Databases 11 Recommendations Product-CatalogShopping-Cart Sales-HistoryCustomer { “userID": 239178239, “productID”: 128623883, “number": 5, “price”: 12.20, } { “userID": 239178239, “productID”: 128623883, “number": 5, “price”: 12.20, } { “Name": "Smith", “lastLogin”: “2012-11-01", “Visits": 121, “shipping address”: “abc”, “shipping address”: “def” } { “Name": "Meyer", “lastLogin”: “2012-11-21", “Visits": 20, “shipping address”: “xyz”, } 423453453 4328, “shirt”, “L”, 1, 12.99 6378, “sweater”, “M”, 2, 37.95 3245, “sweater”, “blue”, 1, 99.95 3245, “pants”, “32/34”, “black”, 1, 99.95 => 874365563 5463, “shirt”, “S”, 1, 9.99 6378, “sweater”, “M”, 2, 37.95 3245, “pants”, “32/34”, “black”, 1, 99.95 => { “type“: "pants", “waist": 32, “length”: 34, “color": "blue", “material”: “cotton" } { “type“: "television", “diagonal screen size": 46, “hdmi inputs": 3, “wall mountable": true, “built-in digital tuner": true, “dynamic contrast ratio”: “50,000:1”, Resolution”: “1920x1080” } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" } { “type": "sweater", “color": "blue", “size": “M”, “material”: “wool”, “form”: “turtleneck" } DocumentStore GraphStore DocumentStore DocumentStoreKeyValueStore
  • 21.
    My four favoritefeatures of ‣ AQL offering joins & traversals ‣ ACID including Multi Collection Transactions ‣ MULTI-MODEL stores graphs and documents 12
  • 22.
    My four favoritefeatures of ‣ AQL offering joins & traversals ‣ ACID including Multi Collection Transactions ‣ MULTI-MODEL stores graphs and documents 12 ‣ FOXX extend the API and adapt it to your needs
  • 23.
    AQL 13 FOR user INusers RETURN user
  • 24.
    AQL 14 FOR user INusers FILTER user.name == "alice" RETURN user
  • 25.
    AQL 15 FOR user INusers FILTER user.name == "alice" FOR invoice IN invoices FILTER user._key == invoice.customer RETURN { user: user, invoice: invoice }
  • 26.
    AQL 16 FOR user INusers FILTER user.name == "alice" RETURN { user: user, invoices: ( FOR invoice IN invoices FILTER user._key == invoice.customer RETURN invoice ) }
  • 27.
    AQL 17 FOR user INusers FILTER user.name == "alice" RETURN { user: user, hasToPay: SUM( FOR invoice IN invoices FILTER user._key == invoice.customer FILTER !invoice.payed RETURN invoice.price ) }
  • 28.
    AQL - Alternative 18 FORuser IN users FILTER user.name == "alice" FOR invoice IN invoices FILTER user._key == invoice.customer FILTER !invoice.payed COLLECT u = user AGGREGATE toPay = SUM(invoice.price) RETURN { user: u, hasToPay: toPay }
  • 29.
    AQL 19 FOR user INusers FILTER user.name == "alice" FOR product IN OUTBOUND user has_bought RETURN product
  • 30.
    AQL 20 FOR user INusers FILTER user.name == "alice" FOR product IN OUTBOUND user has_bought LIMIT 10 RETURN product
  • 31.
    AQL 21 FOR user INusers FILTER user.name == "alice" FOR product, action IN OUTBOUND user has_bought SORT action.timestamp DESC LIMIT 10 RETURN product
  • 32.
    AQL 22 FOR user INusers FILTER user.name == "alice" FOR recommendation IN 3 ANY user has_bought OPTIONS { bfs: true, uniqueVertices: "global" } LIMIT 10 RETURN recommendation
  • 33.
    AQL 23 FOR user INusers FILTER user.name == "alice" FOR recommendation, action, path IN 3 ANY user has_bought FILTER path.vertices[2].age <= user.age + 5 AND path.vertices[2].age >= user.age - 5 LIMIT 10 RETURN recommendation
  • 34.
    AQL 24 FOR user INusers FILTER user.name == "alice" FOR recommendation, action, path IN 3 ANY user has_bought FILTER path.vertices[2].age <= user.age + 5 AND path.vertices[2].age >= user.age - 5 FILTER recommendation.price < 25 LIMIT 10 RETURN recommendation
  • 35.
    ACID - Transactions ‣Invoke a transaction: db._executeTransaction({ collections: { write: ["users", "products"], read: "has_bought" }, action: function() { // all operations go here } }); 25
  • 36.
    ACID - Transactions ‣Invoke a transaction: db._executeTransaction({ collections: { write: ["users", "products"], read: "has_bought" }, action: function() { // all operations go here } }); 25 throw "failure"; // Triggers rollback
  • 37.
    ‣ Native mappingof data into DB ‣ DB optimized ‣ Queries are tailored for your data format ‣ Focus on writing business logic 26 ‣ Data has to be stored redundantly and has to be kept in sync ‣ Several technologies involved ‣ Administration effort is huge Benefits Overhead&
  • 38.
    ‣ Native mappingof data into DB ‣ DB optimized ‣ Queries are tailored for your data format ‣ Focus on writing business logic 26 ‣ One technology involved Benefits Overhead&
  • 39.
  • 40.
    Foxx ‣ Add yourown customized and versioned REST-API on top of ArangoDB in JavaScript ‣ Include as a microservice in Rails, Node.js etc. ‣ Ship an administration fronted with it ‣ Built-in authentication using OAuth2.0 or HTTP-Basic Auth ‣ Operations are encapsulated in the database ‣ low network traffic, direct data access ‣ increases data privacy ➡ Multi-device setups ➡ Microservice Architectures / (~( ) ) /_/ ( _-----_(@ @) ( / /|/--| V " " " " 28
  • 41.
    Foxx Example 29 router.get("/recommend/:price", function(req,res) { res.json(db._query( }); { maxPrice: req.params("price"), name: req.session.username }).toArray()); `FOR user IN users FILTER user.name == @name FOR recommendation, action, path IN 3 ANY user has_bought OPTIONS { bfs: true, uniqueVertices: "global" } FILTER path.vertices[2].age <= user.age + 5 AND path.vertices[2].age >= user.age - 5 FILTER recommendation.price < @maxPrice LIMIT 10 RETURN recommendation`,
  • 42.
    Does it Scale? ‣Sharding (Huge Dataset, Write-Scaling) ‣ Collection: distributed across several servers ‣ Distributed by: List of Attributes (default: _key) ‣ Number of Shards immutable ‣ Has to be defined on creation ‣ Can be different for all collections ‣ Suggested: #Servers 30 2
  • 43.
    Does it Scale? ‣Sharding (Huge Dataset, Write-Scaling) ‣ Collection: distributed across several servers ‣ Distributed by: List of Attributes (default: _key) ‣ Number of Shards immutable ‣ Has to be defined on creation ‣ Can be different for all collections ‣ Suggested: #Servers 30 2 ‣ Replication (Failover, Read-Scaling) ‣ Shard: can have n Followers (Replicas) ‣ Followers: ‣ do not accept writes ‣ synchronous (identical data) ‣ placed on different machine (if possible)
  • 44.
  • 45.
  • 46.
  • 47.
    ‣ Connects thecluster ‣ Ressource management ‣ Knows which servers are online ‣ Knows which resources they have 34
  • 48.
    Marathon ‣ Builds ontop of Mesos ‣ Application Monitor ‣ Can start new applications ‣ "Monitors" running applications ‣ If a machine/process dies Marathon restarts it ‣ Can stop applications ➡ Can scale up / down running applications within a cluster ‣ Offers available resources to new applications ‣ If Marathon dies it is restarted somewhere else 35
  • 49.
    ‣ Builds ontop of Marathon ‣ "Data-Center-Operating-System" ‣ Offers one-click installers for applications (DC/OS Universe) ‣ Includes Service Discovery ‣ Includes Reverse Proxying ➡ You just run an Application through DC/OS and you can communicate with it without ever knowing any IP address 36
  • 50.
    Frameworks ‣ Marathons littlehelpers ‣ Know details about complete Applications ‣ Communicate with Marathon to order sub-processes ‣ Can describe additional conditions for processes ‣ Like: "Do not run all DB instances on the same Machine" ‣ Can trigger marathon to scale up/down processes ➡ ArangoDB has a Marathon Framework 37
  • 51.
  • 52.
    Is Mesosphere required? ‣ArangoDB can run clusters without it ‣ Setup Requires manual effort (can be scripted): ‣ Configure IP addresses ‣ Correct startup ordering ‣ This works: ‣ Automatic Failover (Follower takes over if leader dies) ‣ Rebalancing of shards ‣ Everything inside of ArangoDB ‣ This is based on Mesos: ‣ Complete self healing ‣ Automatic restart of ArangoDBs (on new machines) ➡We suggest you have someone on call 39
  • 53.
    Does your data-modelscale? ‣ Rule of thumb: "The more complex the query, the less it scales". ‣ Indexed-Attribute lookups: ‣ Scale "infinitely" ‣ Examples ‣ Key/Value ‣ FOR doc IN sharded FILTER doc.name == 'Michael' ‣ Joins: ‣ Each join operation requires one additional round-trip (find left side, than find right side) ‣ Scale "okayish" ‣ Graphs: ‣ Each search depth potentially requires 2 join-like operations ‣ A single-server needs to hold a large intermediate result ‣ Does not scale too good 40
  • 54.
    ‣ open sourceand free (Apache 2 license) ‣ sharding & replication ‣ JavaScript throughout (V8 built into server) ‣ drivers for a wide range of languages ‣ web frontend ‣ good & complete documentation ‣ professional as well as community support 41 An overview of other features
  • 55.
    What about Java? ‣Basic Driver developed in-house ‣ Tutorial: https://www.arangodb.com/tutorials/tutorial-java/ ‣ We are working on a Spring-Data integration ‣ We are very happy to get input on this ‣ Feedback ‣ Feature Requests ‣ Personal Opinion on other Drivers/Integration you worked with ‣ Development 42
  • 56.
    Join our growingcommunity 43 .. working on the geo index, the full text search and many APIs: Ruby, Python, PHP, Java, D, Javascript, ...
  • 57.
    Thank you ‣ Furtherquestions? ‣ Follow us on twitter: @arangodb ‣ Join or community slack: arangodb-community.slack.com ‣ Join or google group: https://groups.google.com/forum/#!forum/arangodb ‣ Follow me on twitter/github: @mchacki ‣ Write me a mail: michael@arangodb.com 44