DBMS > RocksDB vs. Sphinx vs. TerarkDB

System Properties Comparison RocksDB vs. Sphinx vs. TerarkDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Key-value store

Search engine

Key-value store

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

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Score	6.03
Rank	#60	Overall
	#6	Search engines

Score	0.04
Rank	#377	Overall
	#58	Key-value stores

Website

rocksdb.org

sphinxsearch.com

github.com/bytedance/terarkdb

Technical documentation

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Facebook, Inc.

Sphinx Technologies Inc.

ByteDance, originally Terark

Initial release

2013

2001

2016

Current release

8.11.4, April 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

BSD

Open Source

GPL version 2, commercial licence available

commercial

restricted open source version available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Server operating systems

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

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-like query language (SphinxQL)

APIs and other access methods

C++ API
Java API

Proprietary protocol

C++ API
Java API

Supported programming languages

C
C++
Go
Java
Perl
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C++
Java

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

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

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Foreign keys

Referential integrity

Transaction concepts

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

yes

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

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.