DBMS > Alibaba Cloud Table Store vs. Amazon DynamoDB vs. Amazon Neptune vs. CockroachDB vs. Tarantool

System Properties Comparison Alibaba Cloud Table Store vs. Amazon DynamoDB vs. Amazon Neptune vs. CockroachDB vs. Tarantool

Editorial information provided by DB-Engines

Name

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

Fast, reliable graph database built for the cloud

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.

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Wide column store

Document store
Key-value store

Graph DBMS
RDF store

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.26
Rank	#301	Overall
	#12	Wide column stores

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

Score	2.20
Rank	#119	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

www.alibabacloud.com/product/table-store

aws.amazon.com/dynamodb

aws.amazon.com/neptune

www.cockroachlabs.com

www.tarantool.io

Technical documentation

www.alibabacloud.com/help/en/tablestore

docs.aws.amazon.com/dynamodb

aws.amazon.com/neptune/developer-resources

www.cockroachlabs.com/docs

www.tarantool.io/en/doc

Developer

Alibaba

Amazon

Cockroach Labs

Initial release

2016

2012

2017

2015

2008

Current release

24.1.0, May 2024

2.10.0, May 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

Apache 2.0, commercial license available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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 and C++

Server operating systems

hosted

Linux
macOS
Windows

BSD
Linux
macOS

Data scheme

schema-free

dynamic schema

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

Full-featured ANSI SQL support

APIs and other access methods

HTTP API

RESTful HTTP API

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

JDBC

Open binary protocol

Supported programming languages

Java
Python

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

Lua, C and SQL stored procedures

Triggers

yes

by integration with AWS Lambda

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

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

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

Multi-source replication using RAFT

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

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

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

with encyption-at-rest

yes

yes, write ahead logging

In-memory capabilities

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

yes, full featured in-memory storage engine with persistence

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)

Role-based access control

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and 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.