DBMS > EJDB vs. Graph Engine vs. Heroic vs. IRONdb vs. RocksDB

System Properties Comparison EJDB vs. Graph Engine vs. Heroic vs. IRONdb vs. RocksDB

Editorial information provided by DB-Engines

Name

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

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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

Primary database model

Document store

Graph DBMS
Key-value store

Time Series DBMS

Key-value store

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

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

Website

github.com/Softmotions/ejdb

www.graphengine.io

github.com/spotify/heroic

www.circonus.com/solutions/time-series-database/

rocksdb.org

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

www.graphengine.io/docs/manual

spotify.github.io/heroic

docs.circonus.com/irondb/category/getting-started

github.com/facebook/rocksdb/wiki

Developer

Softmotions

Microsoft

Spotify

Circonus LLC.

Facebook, Inc.

Initial release

2012

2010

2014

2017

2013

Current release

V0.10.20, January 2018

9.2.1, May 2024

License

Commercial or Open Source

Open Source

GPLv2

Open Source

MIT License

Open Source

Apache 2.0

commercial

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

.NET and C

Java

C and C++

C++

Server operating systems

server-less

.NET

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

text, numeric, histograms

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

via Elasticsearch

SQL

Support of SQL

SQL-like query language (Circonus Analytics Query Language: CAQL)

APIs and other access methods

in-process shared library

RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

HTTP API

C++ API
Java API

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

C#
C++
F#
Visual Basic

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

yes, in Lua

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Automatic, metric affinity per node

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

configurable replication factor, datacenter aware

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

yes

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

In-memory capabilities

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

yes

User concepts

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.