DBMS > Datomic vs. InfinityDB vs. IRONdb vs. RocksDB vs. Sphinx

System Properties Comparison Datomic vs. InfinityDB vs. IRONdb vs. RocksDB vs. Sphinx

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 Java embedded Key-Value Store which extends the Java Map interface

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)

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	0.08
Rank	#365	Overall
	#55	Key-value stores

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

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

www.datomic.com

boilerbay.com

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

rocksdb.org

sphinxsearch.com

Technical documentation

docs.datomic.com

boilerbay.com/infinitydb/manual

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

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

Developer

Cognitect

Boiler Bay Inc.

Circonus LLC.

Facebook, Inc.

Sphinx Technologies Inc.

Initial release

2012

2002

2017

2013

2001

Current release

1.0.6735, June 2023

4.0

V0.10.20, January 2018

9.2.1, May 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

BSD

Open Source

GPL version 2, commercial licence available

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

Java

C and C++

C++

Server operating systems

All OS with a Java VM

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

schema-free

yes

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

manual creation possible, using inversions based on multi-value capability

yes

full-text index on all search fields

SQL

Support of SQL

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

SQL-like query language (SphinxQL)

APIs and other access methods

RESTful HTTP API

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

HTTP API

C++ API
Java API

Proprietary protocol

Supported programming languages

Clojure
Java

Java

.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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes

Transaction Functions

yes, in Lua

Triggers

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

none

Automatic, metric affinity per node

horizontal partitioning

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

none

configurable replication factor, datacenter aware

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

READ-COMMITTED or SERIALIZED

Immediate consistency per node, eventual consistency across nodes

Foreign keys

Referential integrity

manual creation possible, using inversions based on multi-value capability

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

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

The original contents of fields are not stored in the Sphinx index.

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

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.