DBMS > Citus vs. Elasticsearch vs. RocksDB vs. ToroDB

System Properties Comparison Citus vs. Elasticsearch vs. RocksDB vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Secondary database models

Document store

Document store
Spatial DBMS
Vector DBMS

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

Score	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	135.35
Rank	#7	Overall
	#1	Search engines

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

Website

www.citusdata.com

www.elastic.co/elasticsearch

rocksdb.org

github.com/torodb/server

Technical documentation

docs.citusdata.com

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

github.com/facebook/rocksdb/wiki

Developer

Elastic

Facebook, Inc.

8Kdata

Initial release

2010

2013

2016

Current release

8.1, December 2018

8.6, January 2023

9.2.1, May 2024

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

Open Source

Elastic License

Open Source

BSD

Open Source

AGPL-V3

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

C++

Java

Server operating systems

Linux

All OS with a Java VM

Linux

All OS with a Java 7 VM

Data scheme

yes

schema-free

Flexible type definitions. Once a type is defined, it is persistent

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

All search fields are automatically indexed

SQL

Support of SQL

yes

standard, with numerous extensions

SQL-like query language

APIs and other access methods

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

Java API
RESTful HTTP/JSON API

C++ API
Java API

Supported programming languages

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

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

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.

yes

Triggers

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual Consistency
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

In-memory capabilities

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

Memcached and Redis integration

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

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.