DBMS > AgensGraph vs. EJDB vs. Microsoft Azure Cosmos DB vs. RavenDB vs. TinkerGraph

System Properties Comparison AgensGraph vs. EJDB vs. Microsoft Azure Cosmos DB vs. RavenDB vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Globally distributed, horizontally scalable, multi-model database service

Open Source Operational and Transactional Enterprise NoSQL Document Database

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Graph DBMS
Relational DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Graph DBMS

Secondary database models

Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

bitnine.net/agensgraph

github.com/Softmotions/ejdb

azure.microsoft.com/services/cosmos-db

ravendb.net

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

bitnine.net/documentation

github.com/Softmotions/ejdb/blob/master/README.md

learn.microsoft.com/azure/cosmos-db

ravendb.net/docs

Developer

Bitnine Global Inc.

Softmotions

Microsoft

Hibernating Rhinos

Initial release

2016

2012

2014

2010

2009

Current release

2.1, December 2018

5.4, July 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPLv2

commercial

Open Source

AGPL version 3, commercial license available

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Server operating systems

Linux
OS X
Windows

server-less

hosted

Linux
macOS
Raspberry Pi
Windows

Data scheme

depending on used data model

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

JSON types

yes

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

yes

SQL-like query language

SQL-like query language (RQL)

APIs and other access methods

Cypher Query Language
JDBC

in-process shared library

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

TinkerPop 3

Supported programming languages

C
Java
JavaScript
Python

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Groovy
Java

Server-side scripts

Stored procedures

yes

JavaScript

yes

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

none

Sharding

Implicit feature of the cloud service

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

Implicit feature of the cloud service

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

none

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

yes

Relationships in graphs

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Multi-item ACID transactions with snapshot isolation within a partition

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

optional

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

Authorization levels configured per client per database

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.