DBMS > CrateDB vs. JanusGraph vs. Microsoft Azure Cosmos DB vs. RethinkDB

System Properties Comparison CrateDB vs. JanusGraph vs. Microsoft Azure Cosmos DB vs. RethinkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed Database based on Lucene

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Globally distributed, horizontally scalable, multi-model database service

DBMS for the Web with a mechanism to push updated query results to applications in realtime.

Primary database model

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Graph DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Secondary database models

Relational DBMS

Spatial DBMS

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

Score	0.71
Rank	#227	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#10	Vector DBMS

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

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

Score	2.66
Rank	#107	Overall
	#20	Document stores

Website

cratedb.com

janusgraph.org

azure.microsoft.com/services/cosmos-db

rethinkdb.com

Technical documentation

cratedb.com/docs

docs.janusgraph.org

learn.microsoft.com/azure/cosmos-db

rethinkdb.com/docs

Developer

Crate

Linux Foundation; originally developed as Titan by Aurelius

Microsoft

The Linux Foundation

since July 2017

Initial release

2013

2017

2014

2009

Current release

0.6.3, February 2023

2.4.1, August 2020

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2

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

C++

Server operating systems

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

Linux
OS X
Unix
Windows

hosted

Linux
OS X
Windows

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

string, binary, float, bool, date, geometry

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, but no triggers and constraints, and PostgreSQL compatibility

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC
PostgreSQL wire protocol
Prometheus Remote Read/Write
RESTful HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

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

Supported programming languages

.NET
Erlang
Go

community maintained client
Java
JavaScript (Node.js)

community maintained client
Perl

community maintained client
PHP
Python
R
Ruby

community maintained client
Scala

community maintained client

Clojure
Java
Python

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

community-supported driver
C#

community-supported driver
C++

community-supported driver
Clojure

community-supported driver
Dart

community-supported driver
Erlang

community-supported driver
Go

community-supported driver
Haskell

community-supported driver
Java

official driver
JavaScript (Node.js)

official driver
Lisp

community-supported driver
Lua

community-supported driver
Objective-C

community-supported driver
Perl

community-supported driver
PHP

community-supported driver
Python

official driver
Ruby

official driver
Scala

community-supported driver

Server-side scripts

Stored procedures

user defined functions (Javascript)

yes

JavaScript

Triggers

yes

JavaScript

Client-side triggers through changefeeds

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

Implicit feature of the cloud service

Sharding

range based

Replication methods

Methods for redundantly storing data on multiple nodes

Configurable replication on table/partition-level

yes

Implicit feature of the cloud service

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Read-after-write consistency on record level

Eventual Consistency
Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

unique row identifiers can be used for implementing an optimistic concurrency control strategy

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Atomic single-document operations

Concurrency

Support for concurrent manipulation of data

yes

MVCC based

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

In-memory capabilities

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

User concepts

Access control

rights management via user accounts

User authentification and security via Rexster Graph Server

Access rights can be defined down to the item level

yes

users and table-level permissions

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.