DBMS > Amazon DynamoDB vs. Atos Standard Common Repository vs. CrateDB vs. Microsoft Azure Cosmos DB vs. RavenDB

System Properties Comparison Amazon DynamoDB vs. Atos Standard Common Repository vs. CrateDB vs. Microsoft Azure Cosmos DB vs. RavenDB

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Distributed Database based on Lucene

Globally distributed, horizontally scalable, multi-model database service

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Document store
Key-value store

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Secondary database models

Relational DBMS

Spatial DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	70.06
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	0.69
Rank	#226	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#11	Vector DBMS

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

Score	2.68
Rank	#102	Overall
	#19	Document stores

Website

aws.amazon.com/dynamodb

atos.net/en/convergence-creators/portfolio/standard-common-repository

cratedb.com

azure.microsoft.com/services/cosmos-db

ravendb.net

Technical documentation

docs.aws.amazon.com/dynamodb

cratedb.com/docs

learn.microsoft.com/azure/cosmos-db

ravendb.net/docs

Developer

Amazon

Atos Convergence Creators

Crate

Microsoft

Hibernating Rhinos

Initial release

2012

2016

2013

2014

2010

Current release

1703

5.8.1, August 2024

5.4, July 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

commercial

Open Source

AGPL version 3, commercial license 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

Java

Server operating systems

hosted

Linux

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

hosted

Linux
macOS
Raspberry Pi
Windows

Data scheme

schema-free

Schema and schema-less with LDAP views

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

schema-free

Typing

predefined data types such as float or date

yes

optional

yes

JSON types

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.

yes

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

SQL-like query language (RQL)

APIs and other access methods

RESTful HTTP API

LDAP

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

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

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

All languages with LDAP bindings

.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

.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

Server-side scripts

Stored procedures

user defined functions (Javascript)

JavaScript

yes

Triggers

yes

by integration with AWS Lambda

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Configurable replication on table/partition-level

yes

Implicit feature of the cloud service

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Read-after-write consistency on record level

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.

Foreign keys

Referential integrity

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

Atomic execution of specific operations

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID, Cluster-wide transaction available

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 can be defined via the AWS Identity and Access Management (IAM)

LDAP bind authentication

rights management via user accounts

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.