DBMS > Alibaba Cloud Table Store vs. Amazon DynamoDB vs. EXASOL vs. Google Cloud Datastore vs. TempoIQ

System Properties Comparison Alibaba Cloud Table Store vs. Amazon DynamoDB vs. EXASOL vs. Google Cloud Datastore vs. TempoIQ

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It 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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Wide column store

Document store
Key-value store

Relational DBMS

Document store

Time Series DBMS

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

Score	0.24
Rank	#310	Overall
	#12	Wide column stores

Score	77.57
Rank	#16	Overall
	#2	Document stores
	#2	Key-value stores

Score	2.25
Rank	#120	Overall
	#57	Relational DBMS

Score	4.49
Rank	#79	Overall
	#12	Document stores

Website

www.alibabacloud.com/product/table-store

aws.amazon.com/dynamodb

www.exasol.com

cloud.google.com/datastore

tempoiq.com (offline)

Technical documentation

www.alibabacloud.com/help/en/tablestore

docs.aws.amazon.com/dynamodb

www.exasol.com/resources

cloud.google.com/datastore/docs

Developer

Alibaba

Amazon

Exasol

Google

TempoIQ

Initial release

2016

2012

2000

2008

2012

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

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.

Server operating systems

hosted

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language (GQL)

APIs and other access methods

HTTP API

RESTful HTTP API

.Net
JDBC
ODBC
WebSocket

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

HTTP API

Supported programming languages

Java
Python

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

Java
Lua
Python
R

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

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

using Google App Engine

Triggers

yes

by integration with AWS Lambda

yes

Callbacks using the Google Apps Engine

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Multi-source replication using Paxos

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Hadoop integration

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

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.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

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

Serializable Isolation within Transactions, Read Committed outside of Transactions

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 based on subaccounts and tokens

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

Access rights for users, groups and roles according to SQL-standard

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

simple authentication-based access control

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.