DBMS > Alibaba Cloud TSDB vs. Amazon DynamoDB vs. Google Cloud Datastore vs. IBM Db2 vs. Yanza

System Properties Comparison Alibaba Cloud TSDB vs. Amazon DynamoDB vs. Google Cloud Datastore vs. IBM Db2 vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A stable, reliable, and cost-effective online high-performance time series 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

Common in IBM host environments, 2 different versions for host and Windows/Linux

Time Series DBMS for IoT Applications

Primary database model

Time Series DBMS

Document store
Key-value store

Document store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Time Series DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	0.24
Rank	#306	Overall
	#26	Time Series DBMS

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

Website

www.alibabacloud.com/product/hitsdb

aws.amazon.com/dynamodb

cloud.google.com/datastore

www.ibm.com/products/db2

yanza.com

Technical documentation

www.alibabacloud.com/help/en/time-series-database/latest/what-is-tsdb

docs.aws.amazon.com/dynamodb

cloud.google.com/datastore/docs

www.ibm.com/docs/en/db2

Developer

Alibaba

Amazon

Google

IBM

Yanza

Initial release

2012

2008

1983

host version

2015

Current release

12.1, October 2016

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

free version is available

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

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

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

Numeric data and Strings

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

SQL-like query language (GQL)

yes

APIs and other access methods

HTTP REST

RESTful HTTP API

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

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

HTTP API

Supported programming languages

Java

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

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

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

any language that supports HTTP calls

Server-side scripts

Stored procedures

using Google App Engine

yes

Triggers

yes

by integration with AWS Lambda

Callbacks using the Google Apps Engine

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

yes

with separate tools (MQ, InfoSphere)

none

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

yes

via ReferenceProperties or Ancestor paths

yes

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

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 managed on TSDB instance level

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.