DBMS > Alibaba Cloud Table Store vs. Amazon DynamoDB vs. Atos Standard Common Repository vs. Couchbase vs. RavenDB

System Properties Comparison Alibaba Cloud Table Store vs. Amazon DynamoDB vs. Atos Standard Common Repository vs. Couchbase vs. RavenDB

Editorial information provided by DB-Engines

Name

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

Description

A fully managed Wide Column Store for large quantities of semi-structured data with real-time access

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

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Wide column store

Document store
Key-value store

Document store

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.31
Rank	#297	Overall
	#11	Wide column stores

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

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	2.84
Rank	#101	Overall
	#18	Document stores

Website

www.alibabacloud.com/product/table-store

aws.amazon.com/dynamodb

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

www.couchbase.com

ravendb.net

Technical documentation

www.alibabacloud.com/help/en/tablestore

docs.aws.amazon.com/dynamodb

docs.couchbase.com

ravendb.net/docs

Developer

Alibaba

Amazon

Atos Convergence Creators

Couchbase, Inc.

Hibernating Rhinos

Initial release

2016

2012

2016

2011

2010

Current release

1703

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

5.4, July 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

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

C, C++, Go and Erlang

Server operating systems

hosted

Linux

Linux
OS X
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

schema-free

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

yes

optional

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

SQL-like query language (RQL)

APIs and other access methods

HTTP API

RESTful HTTP API

LDAP

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

.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

Java
Python

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

All languages with LDAP bindings

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

yes

Triggers

yes

by integration with AWS Lambda

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

cell division

Automatic Sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication

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

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency or Eventual Consistency depending on configuration

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

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

Atomic single-row operations

ACID

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

Atomic execution of specific operations

ACID

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

Ephemeral buckets

User concepts

Access control

Access rights based on subaccounts and tokens

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

LDAP bind authentication

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

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.