DBMS > CockroachDB vs. Datomic vs. QuestDB vs. RocksDB

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

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

A high performance open source SQL database for time series data

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

Primary database model

Relational DBMS

Time Series DBMS

Key-value store

Secondary database models

Relational DBMS

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

Score	6.10
Rank	#58	Overall
	#33	Relational DBMS

Score	1.76
Rank	#145	Overall
	#66	Relational DBMS

Score	2.48
Rank	#115	Overall
	#9	Time Series DBMS

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

Website

www.cockroachlabs.com

www.datomic.com

questdb.io

rocksdb.org

Technical documentation

www.cockroachlabs.com/docs

docs.datomic.com

questdb.io/docs

github.com/facebook/rocksdb/wiki

Developer

Cockroach Labs

Cognitect

QuestDB Technology Inc

Facebook, Inc.

Initial release

2015

2012

2014

2013

Current release

23.1.1, May 2023

1.0.6735, June 2023

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial

limited edition free

Open Source

Apache 2.0

Open Source

BSD

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

Java (Zero-GC), C++, Rust

C++

Server operating systems

Linux
macOS
Windows

All OS with a Java VM

Linux
macOS
Windows

Linux

Data scheme

dynamic schema

yes

schema-free via InfluxDB Line Protocol

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

SQL

Support of SQL

yes, wire compatible with PostgreSQL

SQL with time-series extensions

APIs and other access methods

JDBC

RESTful HTTP API

HTTP REST
InfluxDB Line Protocol (TCP/UDP)
JDBC
PostgreSQL wire protocol

C++ API
Java API

Supported programming languages

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

Clojure
Java

PostgreSQL driver
C++
Go
Java
JavaScript (Node.js)
Python
Rust

over HTTP

C
C++
Go
Java
Perl
Python
Ruby

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 (by timestamps)

horizontal partitioning

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

Source-replica replication with eventual consistency

yes

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

ACID for single-table writes

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

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

through memory mapped files

yes

User concepts

Access control

Role-based access control

More information provided by the system vendor

Specific characteristics

Relational model with native time series support Column-based storage and time partitioned...
» more

Competitive advantages

High ingestion throughput: peak of 4M rows/sec (TSBS Benchmark) Code optimizations...
» more

Typical application scenarios

Financial tick data Industrial IoT Application Metrics Monitoring
» more

Key customers

Banks & Hedge funds, Yahoo, OKX, Airbus, Aquis Exchange, Net App, Cloudera, Airtel,...
» more

Licensing and pricing models

Open source Apache 2.0 QuestDB Enterprise QuestDB Cloud
» more

News

Does "vpmovzxbd" Scare You? Here's Why it Doesn't Have To
12 April 2024

Create an ADS-B flight radar with QuestDB and a Raspberry Pi
8 April 2024

Build a temperature IoT sensor with Raspberry Pi Pico & QuestDB
5 April 2024

Create an IoT server with QuestDB and a Raspberry Pi
4 April 2024

TimescaleDB vs. QuestDB: Performance benchmarks and overview
27 March 2024

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.