DBMS > Amazon DocumentDB vs. AnzoGraph DB vs. RocksDB vs. Vitess

System Properties Comparison Amazon DocumentDB vs. AnzoGraph DB vs. RocksDB vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Scalable graph database built for online analytics and data harmonization with MPP scaling, high-performance analytical algorithms and reasoning, and virtualization

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	0.29
Rank	#303	Overall
	#25	Graph DBMS
	#14	RDF stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

aws.amazon.com/documentdb

cambridgesemantics.com/anzograph

rocksdb.org

vitess.io

Technical documentation

aws.amazon.com/documentdb/resources

docs.cambridgesemantics.com/anzograph/userdoc/home.htm

github.com/facebook/rocksdb/wiki

vitess.io/docs

Developer

Cambridge Semantics

Facebook, Inc.

The Linux Foundation, PlanetScale

Initial release

2019

2018

2013

Current release

2.3, January 2021

9.2.1, May 2024

15.0.2, December 2022

License

Commercial or Open Source

commercial

free trial version available

Open Source

BSD

Open Source

Apache Version 2.0, commercial licenses available

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

C++

Server operating systems

hosted

Linux

Docker
Linux
macOS

Data scheme

schema-free

Schema-free and OWL/RDFS-schema support

schema-free

yes

Typing

predefined data types such as float or date

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

SQL

Support of SQL

SPARQL and SPARQL* as primary query language. Cypher preview.

yes

with proprietary extensions

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

Apache Mule
gRPC
JDBC
Kafka
OData access for BI tools
OpenCypher
RESTful HTTP API
SPARQL

C++ API
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C++
Java
Python

C
C++
Go
Java
Perl
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

Multi-source replication in MPP-Cluster

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Kerberos/HDFS data loading

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency in MPP-Cluster

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

not needed in graphs

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic single-document operations

ACID

yes

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users and roles

Users with fine-grained authorization concept

no user groups or roles

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.