DBMS > Datomic vs. IRONdb vs. OrigoDB vs. RocksDB vs. SAP SQL Anywhere

System Properties Comparison Datomic vs. IRONdb vs. OrigoDB vs. RocksDB vs. SAP SQL Anywhere

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 fully ACID in-memory object graph database

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

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Relational DBMS

Time Series DBMS

Document store
Object oriented DBMS

Key-value store

Relational DBMS

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

www.datomic.com

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

origodb.com

rocksdb.org

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

docs.datomic.com

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

origodb.com/docs

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Cognitect

Circonus LLC.

Robert Friberg et al

Facebook, Inc.

SAP

formerly Sybase

Initial release

2012

2017

2009

under the name LiveDB

2013

1992

Current release

1.0.6735, June 2023

V0.10.20, January 2018

8.11.4, April 2024

17, July 2015

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

BSD

commercial

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

C++

Server operating systems

All OS with a Java VM

Linux

Linux
Windows

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

yes

Secondary indexes

yes

SQL

Support of SQL

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

yes

APIs and other access methods

RESTful HTTP API

HTTP API

.NET Client API
HTTP API
LINQ

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

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

.Net

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

yes, in Lua

yes

yes, in C/C++, Java, .Net or Perl

Triggers

By using transaction functions

yes

Domain Events

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

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

none

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

Source-replica replication

yes

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

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

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

yes

Write ahead log

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

Role based authorization

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.