DBMS > Datomic vs. IRONdb vs. JanusGraph vs. Postgres-XL vs. RocksDB

System Properties Comparison Datomic vs. IRONdb vs. JanusGraph vs. Postgres-XL vs. RocksDB

Editorial information provided by DB-Engines

Name

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

Description

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

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

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

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

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

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

Website

www.datomic.com

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

janusgraph.org

www.postgres-xl.org

rocksdb.org

Technical documentation

docs.datomic.com

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

docs.janusgraph.org

www.postgres-xl.org/documentation

github.com/facebook/rocksdb/wiki

Developer

Cognitect

Circonus LLC.

Linux Foundation; originally developed as Titan by Aurelius

Facebook, Inc.

Initial release

2012

2017

2014

since 2012, originally named StormDB

2013

Current release

1.0.7075, December 2023

V0.10.20, January 2018

0.6.3, February 2023

10 R1, October 2018

9.2.1, May 2024

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

Apache 2.0

Open Source

Mozilla public 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

Java, Clojure

C and C++

Java

C++

Server operating systems

All OS with a Java VM

Linux

Linux
OS X
Unix
Windows

Linux
macOS

Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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.

yes

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

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

yes

distributed, parallel query execution

APIs and other access methods

RESTful HTTP API

HTTP API

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

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

C++ API
Java API

Supported programming languages

Clojure
Java

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

Clojure
Java
Python

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

yes, in Lua

yes

user defined functions

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Automatic, metric affinity per node

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

configurable replication factor, datacenter aware

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

MVCC

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

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

yes

User concepts

Access control

User authentification and security via Rexster Graph Server

fine grained access rights according to SQL-standard

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.