DBMS > Alibaba Cloud Table Store vs. Citus vs. Coveo vs. Heroic vs. RocksDB

System Properties Comparison Alibaba Cloud Table Store vs. Citus vs. Coveo vs. Heroic vs. RocksDB

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 hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

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)

Primary database model

Secondary database models

Document store

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

Score	0.31
Rank	#297	Overall
	#11	Wide column stores

Score	2.15
Rank	#117	Overall
	#56	Relational DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

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

www.citusdata.com

www.coveo.com

github.com/spotify/heroic

rocksdb.org

Technical documentation

www.alibabacloud.com/help/en/tablestore

docs.citusdata.com

docs.coveo.com

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

Developer

Alibaba

Coveo

Spotify

Facebook, Inc.

Initial release

2016

2010

2012

2014

2013

Current release

8.1, December 2018

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

AGPL, commercial license also available

commercial

Open Source

Apache 2.0

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

Java

C++

Server operating systems

hosted

Linux

hosted

Linux

Data scheme

schema-free

yes

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

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.

yes

specific XML type available, but no XML query functionality

Secondary indexes

yes

via Elasticsearch

SQL

Support of SQL

yes

standard, with numerous extensions

APIs and other access methods

HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

RESTful HTTP API

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

C++ API
Java API

Supported programming languages

Java
Python

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C#
Java
JavaScript
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

yes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

Source-replica replication

other methods possible by using 3rd party extensions

yes

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

Foreign keys

Referential integrity

yes

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

fine grained access rights according to SQL-standard

granular access controls, API key management, content filters

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.