DBMS > Datomic vs. GigaSpaces vs. KairosDB vs. RocksDB

System Properties Comparison Datomic vs. GigaSpaces vs. KairosDB vs. RocksDB

Please select another system to include it in the comparison.

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

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

Distributed Time Series DBMS based on Cassandra or H2

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

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Values are user defined objects

Time Series DBMS

Key-value store

Secondary database models

Graph DBMS
Search engine

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	0.97
Rank	#192	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	0.62
Rank	#239	Overall
	#20	Time Series DBMS

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

Website

www.datomic.com

www.gigaspaces.com

github.com/kairosdb/kairosdb

rocksdb.org

Technical documentation

docs.datomic.com

docs.gigaspaces.com/latest/landing.html

kairosdb.github.io

github.com/facebook/rocksdb/wiki

Developer

Cognitect

Gigaspaces Technologies

Facebook, Inc.

Initial release

2012

2000

2013

Current release

1.0.6735, June 2023

15.5, September 2020

1.2.2, November 2018

8.11.4, April 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache Version 2; Commercial licenses available

Open Source

Apache 2.0

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

Java, C++, .Net

Java

C++

Server operating systems

All OS with a Java VM

Linux
macOS
Solaris
Windows

Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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.

XML can be used for describing objects metadata

Secondary indexes

yes

SQL

Support of SQL

SQL-99 for query and DML statements

APIs and other access methods

RESTful HTTP API

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

Graphite protocol
HTTP REST
Telnet API

C++ API
Java API

Supported programming languages

Clojure
Java

.Net
C++
Java
Python
Scala

Java
JavaScript

Node.js
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

Triggers

By using transaction functions

yes, event driven architecture

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

based on Cassandra

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

selectable replication factor

based on Cassandra

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

Transaction concepts

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

ACID

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

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 access control

simple password-based 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.