DBMS > Alibaba Cloud TSDB vs. Amazon Redshift vs. Atos Standard Common Repository vs. Google Cloud Datastore vs. Yanza

System Properties Comparison Alibaba Cloud TSDB vs. Amazon Redshift vs. Atos Standard Common Repository vs. Google Cloud Datastore vs. Yanza

Editorial information provided by DB-Engines

Name

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

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

Large scale data warehouse service for use with business intelligence tools

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

Time Series DBMS for IoT Applications

Primary database model

Time Series DBMS

Relational DBMS

Document store
Key-value store

Document store

Time Series DBMS

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

Score	0.24
Rank	#306	Overall
	#26	Time Series DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Website

www.alibabacloud.com/product/hitsdb

aws.amazon.com/redshift

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

cloud.google.com/datastore

yanza.com

Technical documentation

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

docs.aws.amazon.com/redshift

cloud.google.com/datastore/docs

Developer

Alibaba

Amazon (based on PostgreSQL)

Atos Convergence Creators

Google

Yanza

Initial release

2012

2016

2008

2015

Current release

1703

License

Commercial or Open Source

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

Java

Server operating systems

hosted

Linux

hosted

Windows

Data scheme

schema-free

yes

Schema and schema-less with LDAP views

schema-free

Typing

predefined data types such as float or date

Numeric data and Strings

yes

optional

yes, details here

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

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (GQL)

APIs and other access methods

HTTP REST

JDBC
ODBC

LDAP

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

HTTP API

Supported programming languages

Java

All languages supporting JDBC/ODBC

All languages with LDAP bindings

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

in Python

using Google App Engine

Triggers

yes

Callbacks using the Google Apps Engine

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

informational only, not enforced by the system

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Atomic execution of specific operations

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

fine grained access rights according to SQL-standard

LDAP bind authentication

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

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.