DBMS > Datomic vs. DuckDB vs. RocksDB vs. Tarantool vs. Yanza

System Properties Comparison Datomic vs. DuckDB vs. RocksDB vs. Tarantool vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza 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

An embeddable, in-process, column-oriented SQL OLAP RDBMS

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Key-value store

Document store
Key-value store
Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	4.57
Rank	#74	Overall
	#40	Relational DBMS

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

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

yanza.com

Technical documentation

docs.datomic.com

duckdb.org/docs

github.com/facebook/rocksdb/wiki

www.tarantool.io/en/doc

Developer

Cognitect

Facebook, Inc.

Yanza

Initial release

2012

2018

2013

2008

2015

Current release

1.0.6735, June 2023

0.10, February 2024

8.11.4, April 2024

2.10.0, May 2022

License

Commercial or Open Source

commercial

limited edition free

Open Source

MIT License

Open Source

BSD

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Clojure

C++

C and C++

Server operating systems

All OS with a Java VM

server-less

Linux

BSD
Linux
macOS

Windows

Data scheme

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

schema-free

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

SQL

Support of SQL

yes

Full-featured ANSI SQL support

APIs and other access methods

RESTful HTTP API

Arrow Database Connectivity (ADBC)
CLI Client
JDBC
ODBC

C++ API
Java API

Open binary protocol

HTTP API

Supported programming languages

Clojure
Java

C
C#

3rd party driver
C++
Crystal

3rd party driver
Go

3rd party driver
Java
Lisp

3rd party driver
Python
R
Ruby

3rd party driver
Rust
Swift
Zig

3rd party driver

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

Transaction Functions

Lua, C and SQL stored procedures

Triggers

By using transaction functions

yes, before/after data modification events, on replication events, client session events

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

none

horizontal partitioning

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

none

yes

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

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

yes

yes, write ahead logging

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

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.