DBMS > Alibaba Cloud Table Store vs. Amazon DocumentDB vs. Amazon DynamoDB vs. Google Cloud Datastore vs. TimescaleDB

System Properties Comparison Alibaba Cloud Table Store vs. Amazon DocumentDB vs. Amazon DynamoDB vs. Google Cloud Datastore vs. TimescaleDB

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

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

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Wide column store

Document store

Document store
Key-value store

Document store

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	0.26
Rank	#301	Overall
	#12	Wide column stores

Score	1.91
Rank	#132	Overall
	#24	Document stores

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

www.alibabacloud.com/product/table-store

aws.amazon.com/documentdb

aws.amazon.com/dynamodb

cloud.google.com/datastore

www.timescale.com

Technical documentation

www.alibabacloud.com/help/en/tablestore

aws.amazon.com/documentdb/resources

docs.aws.amazon.com/dynamodb

cloud.google.com/datastore/docs

docs.timescale.com

Developer

Alibaba

Amazon

Google

Timescale

Initial release

2016

2019

2012

2008

2017

Current release

2.15.0, May 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

Apache 2.0

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

Server operating systems

hosted

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data 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

SQL

Support of SQL

SQL-like query language (GQL)

yes

full PostgreSQL SQL syntax

APIs and other access methods

HTTP API

proprietary protocol using JSON (MongoDB compatible)

RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Java
Python

Go
Java
JavaScript (Node.js)
PHP
Python

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

using Google App Engine

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

by integration with AWS Lambda

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Sharding

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

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

yes

Multi-source replication using Paxos

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

using Google Cloud Dataflow

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 type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

Atomic single-row operations

Atomic single-document operations

ACID

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

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.

User concepts

Access control

Access rights based on subaccounts and tokens

Access rights for users and roles

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.