-
Notifications
You must be signed in to change notification settings - Fork 2
Graph Backend Evaluation
Kadosa Koltai edited this page Oct 17, 2019
·
23 revisions
Neo4j | OrientDB | ArangoDB | JanusGraph | |
---|---|---|---|---|
Official Documentation | link | link | link | link |
Proprietary Query Language | Cypher | - | AQL | - |
Native API | Weird, and relies on AQL for Queries | Relies on SQL for Queries | Nice, but relies on AQL for Queries | ✘ |
REST API | ✔ | ✔ + Spring | ✔ + Spring & Swagger | ✘ |
Gremlin | ✔ | ✔ | Maybe, 3rd party | ✔ |
License | GPL3 | Apache2 | Apache2 | Apache2 |
Note | Largest graph DB | Mainly a document store | Web interface actually showing the graph | Middleware, uses other DB for actual storage |
- Git
- Would probably work
- Hard to query
- Has a plugin to handle EMF files
- GPL2
- Graph database management service/ language / VM
- Licensed under Apache2
- Probably hard to learn
- Nearly every graph database supports it
- community Eclipse plug-in to save EMF to MongoDB (document store)
- requires user to run code
- queries using mongoDB's prop QL
Morsa: Seen only in the title of paper
EMF persistence: given by e, saves XML, requires running code (basically only for plugin dev)
NeoEMF: