DBMS > Amazon DocumentDB vs. MonetDB vs. OrientDB vs. PouchDB vs. RocksDB

System Properties Comparison Amazon DocumentDB vs. MonetDB vs. OrientDB vs. PouchDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

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

A relational database management system that stores data in columns

Multi-model DBMS (Document, Graph, Key/Value)

JavaScript DBMS with an API inspired by CouchDB

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

Primary database model

Document store

Relational DBMS

Document store
Graph DBMS
Key-value store

Document store

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	1.72
Rank	#145	Overall
	#67	Relational DBMS

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

aws.amazon.com/documentdb

Technical documentation

aws.amazon.com/documentdb/resources

www.monetdb.org/Documentation

www.orientdb.com/docs/last/index.html

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

Developer

MonetDB BV

OrientDB LTD; CallidusCloud; SAP

Apache Software Foundation

Facebook, Inc.

Initial release

2019

2004

2010

2012

2013

Current release

Dec2023 (11.49), December 2023

3.2.29, March 2024

7.1.1, June 2019

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

Mozilla Public License 2.0

Open Source

Apache version 2

Open Source

BSD

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

JavaScript

C++

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java JDK (>= JDK 6)

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Data scheme

schema-free

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

schema-free

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

via views

SQL

Support of SQL

yes

SQL 2003 with some extensions

SQL-like query language, no joins

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC
native C library

MAPI library (MonetDB application programming interface)
ODBC

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes, in SQL, C, R

Java, Javascript

View functions in JavaScript

Triggers

yes

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding via remote tables

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

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

none

Source-replica replication available in experimental status

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

could be achieved with distributed queries

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

relationship in graphs

Transaction concepts

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

Atomic single-document operations

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

fine grained access rights according to SQL-standard

Access rights for users and roles; record level security configurable

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.