DBMS > Alibaba Cloud Table Store vs. Galaxybase vs. Heroic vs. RocksDB vs. Vitess

System Properties Comparison Alibaba Cloud Table Store vs. Galaxybase vs. Heroic vs. RocksDB vs. Vitess

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

Scalable, ACID-compliant native distributed parallel graph platform

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.31
Rank	#297	Overall
	#11	Wide column stores

Score	0.07
Rank	#377	Overall
	#40	Graph DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

www.alibabacloud.com/product/table-store

galaxybase.com

github.com/spotify/heroic

rocksdb.org

vitess.io

Technical documentation

www.alibabacloud.com/help/en/tablestore

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

vitess.io/docs

Developer

Alibaba

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

Spotify

Facebook, Inc.

The Linux Foundation, PlanetScale

Initial release

2016

2017

2014

2013

Current release

Nov 20, November 2021

9.2.1, May 2024

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

BSD

Open Source

Apache Version 2.0, commercial licenses available

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

C and Java

Java

C++

Server operating systems

hosted

Linux

Docker
Linux
macOS

Data scheme

schema-free

Strong typed schema

schema-free

yes

Typing

predefined data types such as float or date

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

via Elasticsearch

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

HTTP API

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

C++ API
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Java
Python

Go
Java
Python

C
C++
Go
Java
Perl
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined procedures and functions

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic single-row operations

ACID

yes

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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 rights based on subaccounts and tokens

Role-based access control

Users with fine-grained authorization concept

no user groups or roles

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.