DBMS > Alibaba Cloud Table Store vs. Graph Engine vs. Lovefield vs. OpenTSDB vs. Snowflake

System Properties Comparison Alibaba Cloud Table Store vs. Graph Engine vs. Lovefield vs. OpenTSDB vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

A fully managed Wide Column Store for large quantities of semi-structured data with real-time access

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Embeddable relational database for web apps written in pure JavaScript

Scalable Time Series DBMS based on HBase

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

Primary database model

Wide column store

Graph DBMS
Key-value store

Relational DBMS

Time Series DBMS

Relational DBMS

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

Score	0.26
Rank	#301	Overall
	#12	Wide column stores

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	1.68
Rank	#146	Overall
	#12	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.alibabacloud.com/product/table-store

www.graphengine.io

google.github.io/lovefield

opentsdb.net

www.snowflake.com

Technical documentation

www.alibabacloud.com/help/en/tablestore

www.graphengine.io/docs/manual

github.com/google/lovefield/blob/master/docs/spec_index.md

opentsdb.net/docs/build/html/index.html

docs.snowflake.net/manuals/index.html

Developer

Alibaba

Microsoft

Google

currently maintained by Yahoo and other contributors

Snowflake Computing Inc.

Initial release

2016

2010

2014

2011

2014

Current release

2.1.12, February 2017

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

Apache 2.0

Open Source

LGPL

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

.NET and C

JavaScript

Java

Server operating systems

hosted

.NET

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux
Windows

hosted

Data scheme

schema-free

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

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

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

yes

APIs and other access methods

HTTP API

RESTful HTTP API

HTTP API
Telnet API

CLI Client
JDBC
ODBC

Supported programming languages

Java
Python

C#
C++
F#
Visual Basic

JavaScript

Erlang
Go
Java
Python
R
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

Using read-only observers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

horizontal partitioning

none

Sharding

based on HBase

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

none

selectable replication factor

based on HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

User concepts

Access control

Access rights based on subaccounts and tokens

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.