DBMS > Datomic vs. Ignite vs. RocksDB vs. SAP SQL Anywhere vs. XTDB

System Properties Comparison Datomic vs. Ignite vs. RocksDB vs. SAP SQL Anywhere vs. XTDB

Editorial information provided by DB-Engines

Name

Description

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

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

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

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Key-value store

Relational DBMS

Document store

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

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

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.datomic.com

ignite.apache.org

rocksdb.org

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

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.datomic.com

apacheignite.readme.io/docs

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

www.xtdb.com/docs

Developer

Cognitect

Apache Software Foundation

Facebook, Inc.

SAP

formerly Sybase

Juxt Ltd.

Initial release

2012

2015

2013

1992

2019

Current release

1.0.6735, June 2023

Apache Ignite 2.6

8.11.4, April 2024

17, July 2015

1.19, September 2021

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache 2.0

Open Source

BSD

commercial

Open Source

MIT License

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++, Java, .Net

C++

Clojure

Server operating systems

All OS with a Java VM

Linux
OS X
Solaris
Windows

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

Secondary indexes

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

Clojure
Java

C#
C++
Java
PHP
Python
Ruby
Scala

C
C++
Go
Java
Perl
Python
Ruby

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

Clojure
Java

Server-side scripts

Stored procedures

yes

Transaction Functions

yes (compute grid and cache interceptors can be used instead)

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

Triggers

By using transaction functions

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

yes (replicated cache)

yes

Source-replica replication

Database mirroring

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

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

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

Security Hooks for custom implementations

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.