DBMS > Datomic vs. Oracle Berkeley DB vs. Quasardb vs. RocksDB

System Properties Comparison Datomic vs. Oracle Berkeley DB vs. Quasardb 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

Widely used in-process key-value store

Distributed, high-performance timeseries database

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

Primary database model

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Time Series DBMS

Key-value store

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

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.14
Rank	#332	Overall
	#29	Time Series DBMS

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

Website

www.datomic.com

www.oracle.com/database/technologies/related/berkeleydb.html

quasar.ai

rocksdb.org

Technical documentation

docs.datomic.com

docs.oracle.com/cd/E17076_05/html/index.html

doc.quasar.ai/master

github.com/facebook/rocksdb/wiki

Developer

Cognitect

Oracle

originally developed by Sleepycat, which was acquired by Oracle

quasardb

Facebook, Inc.

Initial release

2012

1994

2009

2013

Current release

1.0.6735, June 2023

18.1.40, May 2020

3.14.1, January 2024

9.2.1, May 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

commercial license available

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

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

C, Java, C++ (depending on the Berkeley DB edition)

C++

Server operating systems

All OS with a Java VM

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

BSD
Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

integer and binary

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

only with the Berkeley DB XML edition

Secondary indexes

yes

with tags

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

SQL-like query language

APIs and other access methods

RESTful HTTP API

HTTP API

C++ API
Java API

Supported programming languages

Clojure
Java

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

Triggers

By using transaction functions

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

none

Sharding

consistent hashing

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

Source-replica replication

Source-replica replication with selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

by using LevelDB

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

Transient mode

yes

User concepts

Access control

Cryptographically strong user authentication and audit trail

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.