DBMS > Amazon DocumentDB vs. CockroachDB vs. Coveo vs. EsgynDB vs. RocksDB

System Properties Comparison Amazon DocumentDB vs. CockroachDB vs. Coveo vs. EsgynDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

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

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

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

Primary database model

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

Score	1.91
Rank	#131	Overall
	#24	Document stores

Score	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

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

Website

aws.amazon.com/documentdb

www.cockroachlabs.com

www.coveo.com

www.esgyn.cn

rocksdb.org

Technical documentation

aws.amazon.com/documentdb/resources

www.cockroachlabs.com/docs

docs.coveo.com

github.com/facebook/rocksdb/wiki

Developer

Cockroach Labs

Coveo

Esgyn

Facebook, Inc.

Initial release

2019

2015

2012

2015

2013

Current release

24.1.0, May 2024

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0, commercial license available

commercial

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

C++, Java

C++

Server operating systems

hosted

Linux
macOS
Windows

hosted

Linux

Data scheme

schema-free

dynamic schema

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

yes

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

SQL

Support of SQL

yes, wire compatible with PostgreSQL

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

JDBC

RESTful HTTP API

ADO.NET
JDBC
ODBC

C++ API
Java API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

C#
Java
JavaScript
Python

All languages supporting JDBC/ODBC/ADO.Net

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

yes

Sharding

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

Multi-source replication using RAFT

yes

Multi-source replication between multi datacenters

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

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

Atomic single-document operations

ACID

yes

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

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

Role-based access control

granular access controls, API key management, content filters

fine grained access rights according to SQL-standard

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.