DBMS > BigchainDB vs. Datomic vs. Elasticsearch vs. RocksDB

System Properties Comparison BigchainDB vs. Datomic vs. Elasticsearch vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

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

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)

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	132.83
Rank	#7	Overall
	#1	Search engines

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

www.bigchaindb.com

www.datomic.com

www.elastic.co/elasticsearch

rocksdb.org

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.datomic.com

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

github.com/facebook/rocksdb/wiki

Developer

Cognitect

Elastic

Facebook, Inc.

Initial release

2016

2012

2010

2013

Current release

1.0.7075, December 2023

8.6, January 2023

9.2.1, May 2024

License

Commercial or Open Source

Open Source

AGPL v3

commercial

limited edition free

Open Source

Elastic License

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

Python

Java, Clojure

Java

C++

Server operating systems

Linux

All OS with a Java VM

Linux

Data scheme

schema-free

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

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

SQL

Support of SQL

SQL-like query language

APIs and other access methods

CLI Client
RESTful HTTP API

RESTful HTTP API

Java API
RESTful HTTP/JSON API

C++ API
Java API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

Clojure
Java

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

Triggers

By using transaction functions

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

But extensive use of caching in the application peers

yes

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

Foreign keys

Referential integrity

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,with MongoDB ord RethinkDB

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

Memcached and Redis integration

yes

User concepts

Access control

yes

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.