DBMS > Datomic vs. IRONdb vs. KeyDB vs. RocksDB vs. YTsaurus

System Properties Comparison Datomic vs. IRONdb vs. KeyDB vs. RocksDB vs. YTsaurus

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

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

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

YTsaurus is an open source platform for distributed storage and processing.

Primary database model

Relational DBMS

Time Series DBMS

Key-value store

Document store
Key-value store

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

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

Score	0.21
Rank	#324	Overall
	#45	Document stores
	#48	Key-value stores

Website

www.datomic.com

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

github.com/Snapchat/KeyDB
keydb.dev

rocksdb.org

ytsaurus.tech

Technical documentation

docs.datomic.com

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

docs.keydb.dev

github.com/facebook/rocksdb/wiki

ytsaurus.tech/docs/en

Developer

Cognitect

Circonus LLC.

EQ Alpha Technology Ltd.

Facebook, Inc.

Yandex

Initial release

2012

2017

2019

2013

2023

Current release

1.0.7075, December 2023

V0.10.20, January 2018

9.2.1, May 2024

License

Commercial or Open Source

commercial

limited edition free

commercial

Open Source

BSD-3

Open Source

BSD

Open Source

Apache License, Version 2.0

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

Ubuntu

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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.

Secondary indexes

yes

by using the Redis Search module

SQL

Support of SQL

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

YQL, an SQL-based language, is supported

APIs and other access methods

RESTful HTTP API

HTTP API

Proprietary protocol

RESP - REdis Serialization Protoco

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

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

C
C++
Go
Java
Perl
Python
Ruby

C++
Go
Java
JavaScript
Python

Server-side scripts

Stored procedures

yes

Transaction Functions

yes, in Lua

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

Automatic, metric affinity per node

Sharding

horizontal partitioning

Sharding

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

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Eventual Consistency
Strong eventual consistency with CRDTs

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Optimistic locking, atomic execution of commands blocks and scripts

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

Configurable mechanisms for persistency via snapshots and/or operations logs

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

simple password-based access control and ACL

Access Control Lists

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.