DBMS > Alibaba Cloud Table Store vs. FoundationDB vs. Heroic vs. Hypertable vs. RocksDB

System Properties Comparison Alibaba Cloud Table Store vs. FoundationDB vs. Heroic vs. Hypertable vs. RocksDB

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the ranking.

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

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

Ordered key-value store. Core features are complimented by layers.

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

An open source BigTable implementation based on distributed file systems such as Hadoop

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

Primary database model

Wide column store

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Time Series DBMS

Wide column store

Key-value store

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

Score	0.31
Rank	#297	Overall
	#11	Wide column stores

Score	1.06
Rank	#185	Overall
	#31	Document stores
	#28	Key-value stores
	#85	Relational DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

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

Website

www.alibabacloud.com/product/table-store

github.com/apple/foundationdb

github.com/spotify/heroic

rocksdb.org

Technical documentation

www.alibabacloud.com/help/en/tablestore

apple.github.io/foundationdb

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

Developer

Alibaba

FoundationDB

Spotify

Hypertable Inc.

Facebook, Inc.

Initial release

2016

2013

2014

2009

2013

Current release

6.2.28, November 2020

0.9.8.11, March 2016

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

GNU version 3. Commercial license available

Open Source

BSD

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++

Java

C++

Server operating systems

hosted

Linux
OS X
Windows

an inofficial Windows port is available

Linux

Data scheme

schema-free

some layers support schemas

schema-free

Typing

predefined data types such as float or date

yes

some layers support typing

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

restricted

only exact value or prefix value scans

SQL

Support of SQL

supported in specific SQL layer only

APIs and other access methods

HTTP API

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

C++ API
Thrift

C++ API
Java API

Supported programming languages

Java
Python

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

C++
Java
Perl
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

in SQL-layer only

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes

selectable replication factor on file system level

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Linearizable consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

in SQL-layer only

Transaction concepts

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

Atomic single-row operations

ACID

yes

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

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.