DBMS > Alibaba Cloud TSDB vs. Apache Phoenix vs. Google Cloud Datastore vs. Riak KV vs. Snowflake

System Properties Comparison Alibaba Cloud TSDB vs. Apache Phoenix vs. Google Cloud Datastore vs. Riak KV vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

A stable, reliable, and cost-effective online high-performance time series database service

A scale-out RDBMS with evolutionary schema built on Apache HBase

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

Distributed, fault tolerant key-value store

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

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

Score	0.24
Rank	#306	Overall
	#26	Time Series DBMS

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.alibabacloud.com/product/hitsdb

phoenix.apache.org

cloud.google.com/datastore

www.snowflake.com

Technical documentation

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

phoenix.apache.org

cloud.google.com/datastore/docs

www.tiot.jp/riak-docs/riak/kv/latest

docs.snowflake.net/manuals/index.html

Developer

Alibaba

Apache Software Foundation

Google

OpenSource, formerly Basho Technologies

Snowflake Computing Inc.

Initial release

2014

2008

2009

2014

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

Apache version 2, commercial enterprise edition

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.

Implementation language

Java

Erlang

Server operating systems

hosted

Linux
Unix
Windows

hosted

Linux
OS X

hosted

Data scheme

schema-free

yes

late-bound, schema-on-read capabilities

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

SQL-like query language (GQL)

yes

APIs and other access methods

HTTP REST

JDBC

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

HTTP API
Native Erlang Interface

CLI Client
JDBC
ODBC

Supported programming languages

Java

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

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

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

using Google App Engine

Erlang

user defined functions

Triggers

Callbacks using the Google Apps Engine

yes

pre-commit hooks and post-commit hooks

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication using Paxos

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual 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.

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

links between data sets can be stored

yes

Transaction concepts

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

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.

yes

User concepts

Access control

Access managed on TSDB instance level

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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

yes, using Riak Security

Users with fine-grained authorization concept, user roles and pluggable authentication

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.