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

System Properties Comparison Alibaba Cloud TSDB vs. Apache Phoenix vs. Bangdb vs. Google Cloud Datastore 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

Converged and high performance database for device data, events, time series, document and graph

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

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

Primary database model

Time Series DBMS

Relational DBMS

Document store
Graph DBMS
Time Series DBMS

Document store

Relational DBMS

Secondary database models

Spatial 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	0.08
Rank	#347	Overall
	#47	Document stores
	#34	Graph DBMS
	#31	Time Series DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.alibabacloud.com/product/hitsdb

phoenix.apache.org

bangdb.com

cloud.google.com/datastore

www.snowflake.com

Technical documentation

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

phoenix.apache.org

docs.bangdb.com

cloud.google.com/datastore/docs

docs.snowflake.net/manuals/index.html

Developer

Alibaba

Apache Software Foundation

Sachin Sinha, BangDB

Google

Snowflake Computing Inc.

Initial release

2014

2012

2008

2014

Current release

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

BangDB 2.0, October 2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

BSD 3

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

C, C++

Server operating systems

hosted

Linux
Unix
Windows

Linux

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: string, long, double, int, geospatial, stream, events

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

secondary, composite, nested, reverse, geospatial

yes

SQL

Support of SQL

yes

SQL like support with command line tool

SQL-like query language (GQL)

yes

APIs and other access methods

HTTP REST

JDBC

Proprietary protocol
RESTful HTTP API

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

CLI Client
JDBC
ODBC

Supported programming languages

Java

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

C
C#
C++
Java
Python

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

using Google App Engine

user defined functions

Triggers

yes, Notifications (with Streaming only)

Callbacks using the Google Apps Engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor, Knob for CAP (enterprise version only)

Multi-source replication using Paxos

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Tunable consistency, set CAP knob accordingly

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

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, optimistic concurrency control

yes

Durability

Support for making data persistent

yes

yes, implements WAL (Write ahead log) as well

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

yes, run db with in-memory only mode

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

yes (enterprise version only)

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

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.