DBMS > CockroachDB vs. Datomic vs. RocksDB vs. Sphinx

System Properties Comparison CockroachDB vs. Datomic vs. RocksDB vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

Primary database model

Relational DBMS

Key-value store

Search engine

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

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

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

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

www.cockroachlabs.com

www.datomic.com

rocksdb.org

sphinxsearch.com

Technical documentation

www.cockroachlabs.com/docs

docs.datomic.com

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

Developer

Cockroach Labs

Cognitect

Facebook, Inc.

Sphinx Technologies Inc.

Initial release

2015

2012

2013

2001

Current release

24.1.0, May 2024

1.0.6735, June 2023

9.2.1, May 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

limited edition free

Open Source

BSD

Open Source

GPL version 2, commercial licence 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

Java, Clojure

C++

Server operating systems

Linux
macOS
Windows

All OS with a Java VM

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

dynamic schema

yes

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

full-text index on all search fields

SQL

Support of SQL

yes, wire compatible with PostgreSQL

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC

RESTful HTTP API

C++ API
Java API

Proprietary protocol

Supported programming languages

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

Clojure
Java

C
C++
Go
Java
Perl
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

Transaction Functions

Triggers

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

none

But extensive use of caching in the application peers

horizontal partitioning

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

none

But extensive use of caching in the application peers

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

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

Role-based 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.