DBMS > Elasticsearch vs. JaguarDB vs. RavenDB vs. RocksDB

System Properties Comparison Elasticsearch vs. JaguarDB vs. RavenDB vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Performant, highly scalable DBMS for AI and IoT applications

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Primary database model

Search engine

Key-value store
Vector DBMS

Document store

Key-value store

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

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

Website

www.elastic.co/elasticsearch

www.jaguardb.com

ravendb.net

rocksdb.org

Technical documentation

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

www.jaguardb.com/support.html

ravendb.net/docs

github.com/facebook/rocksdb/wiki

Developer

Elastic

DataJaguar, Inc.

Hibernating Rhinos

Facebook, Inc.

Initial release

2010

2015

2010

2013

Current release

8.6, January 2023

3.3 July 2023

5.4, July 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Elastic License

Open Source

GPL V3.0

Open Source

AGPL version 3, commercial license available

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

C++

the server part. Clients available in other languages

C++

Server operating systems

All OS with a Java VM

Linux

Linux
macOS
Raspberry Pi
Windows

Linux

Data scheme

schema-free

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

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

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language (RQL)

APIs and other access methods

Java API
RESTful HTTP/JSON API

JDBC
ODBC

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

C++ API
Java API

Supported programming languages

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

Eventual Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

Transaction concepts

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

ACID, Cluster-wide transaction available

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

rights management via user accounts

Authorization levels configured per client per database

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.