DBMS > Elasticsearch vs. OrigoDB vs. RocksDB vs. SQL.JS vs. TerminusDB

System Properties Comparison Elasticsearch vs. OrigoDB vs. RocksDB vs. SQL.JS vs. TerminusDB

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

A fully ACID in-memory object graph database

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

Port of SQLite to JavaScript

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Search engine

Document store
Object oriented DBMS

Key-value store

Relational DBMS

Graph DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

Document store
RDF store

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

Score	132.83
Rank	#7	Overall
	#1	Search engines

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

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

Score	0.63
Rank	#241	Overall
	#112	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

www.elastic.co/elasticsearch

Technical documentation

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

origodb.com/docs

github.com/facebook/rocksdb/wiki

sql.js.org/documentation/index.html

terminusdb.github.io/terminusdb/#

Developer

Elastic

Robert Friberg et al

Facebook, Inc.

Alon Zakai

enhancements implemented by others

DataChemist Ltd.

Initial release

2010

2009

under the name LiveDB

2013

2012

2018

Current release

8.6, January 2023

9.2.1, May 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Elastic License

Open Source

BSD

Open Source

GPL 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++

JavaScript

Prolog, Rust

Server operating systems

All OS with a Java VM

Linux
Windows

Linux

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Data scheme

schema-free

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

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

SQL-like query language (WOQL)

APIs and other access methods

Java API
RESTful HTTP/JSON API

.NET Client API
HTTP API
LINQ

C++ API
Java API

JavaScript API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

.Net

C
C++
Go
Java
Perl
Python
Ruby

JavaScript

JavaScript
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

by using the 'percolation' feature

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

none

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

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

none

Foreign keys

Referential integrity

depending on model

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

except by serializing a db to a file

yes

in-memory journaling

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

Role based authorization

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.