-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy patharangodb.html
688 lines (530 loc) · 11.1 KB
/
arangodb.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
<!DOCTYPE html>
<html>
<head>
<title>ArangoDB</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>
<style type="text/css">
@import url(https://fonts.googleapis.com/css?family=Yanone+Kaffeesatz);
@import url(https://fonts.googleapis.com/css?family=Droid+Serif:400,700,400italic);
@import url(https://fonts.googleapis.com/css?family=Ubuntu+Mono:400,700,400italic);
body { font-family: 'Droid Serif'; }
h1, h2, h3 {
font-family: 'Yanone Kaffeesatz';
font-weight: 400;
}
.remark-slide-content h1 { font-size: 3em; }
.remark-slide-content h2 { font-size: 2em; }
.remark-slide-content h3 { font-size: 1.6em; }
.remark-code, .remark-inline-code { font-family: 'Ubuntu Mono'; }
.pull-left {
float: left;
width: 47%;
}
.pull-right {
float: right;
width: 47%;
}
.left-column {
color: #777;
width: 30%;
height: 92%;
float: left;
}
.left-column h3:last-of-type, .left-column h4:last-child {
color: #000;
}
.right-column {
width: 65%;
float: right;
padding-top: 1em;
}
.content-image img {
width: 100%;
height: 100%;
}
.content-table td {
}
</style>
</head>
<body>
<textarea id="source">
class: center, middle
---
# Agenda
1. Introduction
2. ArangoDB Basics
3. Advanced Features
4. ArangoDB vs MongoDB
5. Conclusion
6. Q & A
---
# Introduction
## Key features:
* multi-model nosql database
* documents
* graphs
* key-values
* transactions
* SQL-like query (AQL)
```javascript
// ArangoDB.explain()
{
"type": "NoSQL database",
"openSource": true,
"version": 2.4.3,
"builtWith": ["C", "C++", "js"],
"javascript": ["client side", "server side"],
"uses": "v8"
}
```
---
# ArangoDB Basics
.left-column[
### Documents and collections
]
.right-column[
* ArangoDB is a database that works with documents
* Documents are sets of name/value pairs (think of JSON objects), e.g.
```json
{
"name": "Jan",
"age": 37
}
```
* Documents are organised in collections (like tables in relational databases)
]
---
# ArangoDB Basics
.left-column[
### Documents and collections
### Data types: JSON
]
.right-column[
* ArangoDB operates on JSON documents
* JSON data can be saved as-is:
```javascript
db.users.save({
"name": "Jan",
"age": 37
});
```
]
---
# ArangoDB Basics
.left-column[
### Documents and collections
### Data types: JSON
### Schema-free
]
.right-column[
* Documents can be heterogenous - even in the same collection
e.g.
```json
{ "name": "Jan", "age": 37 }
{ "name": "Tim", "city": "Paris" }
{ "name": {
"firstname": "Patrick",
"lastname": "Star"
},
"active": true
}
```
]
---
# ArangoDB Basics
.left-column[
### Documents and collections
### Data types: JSON
### Schema-free
### Simple queries
]
.right-column[
* Query a document by its unique id/key:
```javascript
db._document('users/jan');
```
* Query by providing an example:
```javascript
db.users.byExample({ name: 'Jan' });
```
]
---
# ArangoDB Basics
.left-column[
### Documents and collections
### Data types: JSON
### Schema-free
### Simple queries
### Indexes
]
.right-column[
* ArangoDB allows querying on any document attributes or nested attributes
* For each collection there will always be a primary index which is a hash index for the document keys (`_key` attribute)
of all documents in the collection
* Secondary indexes can be created for higher query performances:
* Hash indexes (equality queries)
* Skiplists (range queries)
* 2d geo indexes (location queries)
]
---
# Advanced Features
.left-column[
### References
]
.right-column[
* ArangoDB can store references between documents
* References are documents with two endpoints (document type: Edge)
* Reference documents can carry own attributes
]
---
# Advanced Features
.left-column[
### References
### References example
]
.right-column[
```javascript
// Users documents (document)
{
"name": "Jan",
"age": 37
}
{
"name": "Tim",
"city": "Paris"
}
// Relations documents (edge document)
{
"_from": "users/jan",
"_to": "users/tim",
"type": "knows"
}
{
"_from": "users/tim",
"_to": "users/jan",
"type": "knows"
}
```
]
---
# Advanced Features
.left-column[
### References
### Graph
]
.right-column[
A Graph consists of vertices and edges. Edges are stored as documents in edge collections.
In general a vertex is stored in a document collection.
.content-image[
]
]
---
# Advanced Features
.left-column[
### References
### Graph
### Vertices & Edges
]
.right-column[
```javascript
// Start vertex
{
"_id": "posts/1",
"comment": [
"great post",
"something else"
],
"organization": "n-fuse"
}
// End vertex
{
"_id": "users/tim",
"name": "Tim"
}
// Edge
{
"_id": "created_by/1",
"_from": "posts/1",
"_to": "users/tim"
}
```
]
---
# Advanced Features
.left-column[
### References
### Graph
### Graph definition
]
.right-column[
The graph module adds an additional layer on top of these collections giving you the following guarantees:
* All modifications are executed transactional
* If you delete a vertex all edges will be deleted, you will never have loose ends
* If you insert an edge it is checked if the edge matches the definition, your edge collections will only contain valid edges
#### Warning
These guarantees are lost if you access the collections in any other way than the graph module!!!
]
---
# Advanced Features
.left-column[
### References
### Graph
### Graph example
]
.right-column[
```javascript
var module = require("org/arangodb/general-graph");
// Create an empty graph
var graph = module._create("post");
// Graph can have an arbitrary amount of vertex
// collections, which are not part of
// any edge definition of the graph
graph._addVertexCollection("posts");
graph._addVertexCollection("users");
// Create a graph with edge definitions
// and orphan collections:
var rel = module._relation("created_by", [
"posts"
], [
"users"
]);
graph._extendEdgeDefinitions(rel);
// Show graph definition
graph;
[ Graph post EdgeDefinitions: [
"created_by: [posts] -> [users]"
] VertexCollections: [ ] ]
```
]
---
# Advanced Features
.left-column[
### References
### Graph
### Graph query
]
.right-column[
Graph functions:
* graph._edges(examples)
* graph._vertices(examples)
* graph_query.toVertices(examples)
* graph_query.outEdges(examples)
* etc.
AQL query:
```SQL
// Get all posts of n-fuse organization
// and their coresponding authors
FOR v IN GRAPH_TRAVERSAL("post", {
organization: "n-fuse"
}, "outbound")
RETURN v
```
]
---
# Advanced Features
.left-column[
### References
### Graph
### Transactions
]
.right-column[
Transactions in ArangoDB are atomic, consistent, isolated, and durable (ACID).
* Atomicity: either complete in their entirety or have no effect at all.
* Consistency: no constraints or other invariants will be violated during or after any transaction.
* Isolation: hide the modifications of a transaction from other transactions until the transaction commits.
* Durability: operations from transactions that have committed will be made persistent.
The amount of transaction durability is configurable in ArangoDB, as is the durability on collection level.
]
---
# Advanced Features
.left-column[
### References
### Graph
### Transactions
### Transactions example
]
.right-column[
```javascript
// setup
db._create('c1');
db._create('c2');
db._executeTransaction({
collections: {
write: [ 'c1', 'c1' ]
// i.e. the write mode includes the read mode
// read: [ 'c1' ]
},
action: function () {
var db = require('internal').db;
for (var i = 0; i < 100; ++i) {
db.c1.save({ _key: 'key' + i });
db.c2.save({ _key: 'key' + i });
}
db.c1.count(); // 100
// abort
throw 'something wrong!'
}
});
```
]
---
# Advanced Features
.left-column[
### References
### Graph
### Transactions
### ArangoDB query language (AQL)
]
.right-column[
* ArangoDB can also answer complex SQL-like queries
* Such queries are expressed in ArangoDB's textual query language
* This language allows joins, sub-queries, aggregation etc.
]
---
# Advanced Features
.left-column[
### References
### Graph
### Transactions
### ArangoDB query language (AQL)
### AQL example
]
.right-column[
```sql
For u IN users
FILTER u.city == "Paris" &&
u.age >= 18
LET followers = (
FOR f IN users
FILTER f.follow == u._id
RETURN f
)
RETURN {
"users": u,
"popularity": LENGTH(followers)
}
```
]
---
# MongoDB vs ArangoDB
.left-column[
### Comparison
]
.right-column[
.content-table[
<table style="width:100%">
<thead>
<tr>
<th></th>
<th>ArangoDB</th>
<th>MongoDB</th>
</tr>
</thead>
<tbody>
<tr>
<td>Data model</td>
<td align="center">
<pre>Document-oriented<br/>Graph-oriented<br/>key-value</pre>
</td>
<td align="center">
<pre>Document-oriented</pre>
</td>
</tr>
<tr>
<td>Query language</td>
<td align="center">
<pre>Javascript<br/>API calls<br/>AQL<br/>RESTful</pre>
</td>
<td align="center">
<pre>Javascript<br/>API calls</pre>
</td>
</tr>
<tr>
<td>Data types</td>
<td align="center">
<pre>JSON</pre>
</td>
<td align="center">
<pre>JSON<br/>BLOB</pre>
</td>
</tr>
<tr>
<td>Map reduce</td>
<td align="center">No</td>
<td align="center">Yes</td>
</tr>
</tbody>
</table>
]
]
---
# MongoDB vs ArangoDB
.left-column[
### Comparison
]
.right-column[
.content-table[
<table style="width:100%">
<thead>
<tr>
<th></th>
<th>ArangoDB</th>
<th>MongoDB</th>
</tr>
</thead>
<tbody>
<tr>
<td>Transactions</td>
<td align="center">Yes</td>
<td align="center">No</td>
</tr>
<tr>
<td>Revision control</td>
<td align="center">Yes</td>
<td align="center">No</td>
</tr>
<tr>
<td>Graph support</td>
<td align="center">Yes</td>
<td align="center">No</td>
</tr>
<tr>
<td>Native driver</td>
<td align="center">REST API</td>
<td align="center">BSON</td>
</tr>
</tbody>
</table>
]
]
---
# MongoDB vs ArangoDB
.left-column[
### Comparison
### The most important difference
]
.right-column[
Why we need a more expressive query language ?
.content-image[
]
]
---
# Conclusion
1. Introduction of document reference
2. Complex query with AQL
3. Graph module for future use
---
class: center, middle
# Thank you, any questions?
</textarea>
<script src="https://gnab.github.io/remark/downloads/remark-latest.min.js">
</script>
<script>
var slideshow = remark.create();
</script>
</body>
</html>