DBMS > Alibaba Cloud Table Store vs. Apache Druid vs. RocksDB vs. Sphinx vs. SwayDB

System Properties Comparison Alibaba Cloud Table Store vs. Apache Druid vs. RocksDB vs. Sphinx vs. SwayDB

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

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

Open source search engine for searching in data from different sources, e.g. relational databases

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Wide column store

Relational DBMS
Time Series DBMS

Key-value store

Search engine

Key-value store

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

Score	0.26
Rank	#301	Overall
	#12	Wide column stores

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

www.alibabacloud.com/product/table-store

Technical documentation

www.alibabacloud.com/help/en/tablestore

druid.apache.org/docs/latest/design

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

Developer

Alibaba

Apache Software Foundation and contributors

Facebook, Inc.

Sphinx Technologies Inc.

Simer Plaha

Initial release

2016

2012

2013

2001

2018

Current release

29.0.1, April 2024

9.2.1, May 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache license v2

Open Source

BSD

Open Source

GPL version 2, commercial licence available

Open Source

GNU Affero GPL V3.0

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

Scala

Server operating systems

hosted

Linux
OS X
Unix

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-less columns are supported

schema-free

yes

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.

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

SQL for querying

SQL-like query language (SphinxQL)

APIs and other access methods

HTTP API

JDBC
RESTful HTTP/JSON API

C++ API
Java API

Proprietary protocol

Supported programming languages

Java
Python

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C
C++
Go
Java
Perl
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Java
Kotlin
Scala

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

Sharding

manual/auto, time-based

horizontal partitioning

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

yes, via HDFS, S3 or other storage engines

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic single-row operations

yes

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

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.