DBMS > IRONdb vs. Oracle Berkeley DB vs. RocksDB vs. Splice Machine

System Properties Comparison IRONdb vs. Oracle Berkeley DB vs. RocksDB vs. Splice Machine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Widely used in-process key-value store

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

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

Time Series DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Key-value store

Relational DBMS

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

Score	2.01
Rank	#126	Overall
	#21	Key-value stores
	#3	Native XML DBMS

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

Score	0.54
Rank	#252	Overall
	#115	Relational DBMS

Website

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

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

rocksdb.org

splicemachine.com

Technical documentation

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

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

github.com/facebook/rocksdb/wiki

splicemachine.com/how-it-works

Developer

Circonus LLC.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

Splice Machine

Initial release

2017

1994

2013

2014

Current release

V0.10.20, January 2018

18.1.40, May 2020

9.2.1, May 2024

3.1, March 2021

License

Commercial or Open Source

commercial

Open Source

commercial license available

Open Source

BSD

Open Source

AGPL 3.0, commercial license available

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

C and C++

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

C++

Java

Server operating systems

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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.

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

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

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

HTTP API

C++ API
Java API

JDBC
Native Spark Datasource
ODBC

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

.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

C
C++
Go
Java
Perl
Python
Ruby

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

yes, in Lua

yes

Java

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic, metric affinity per node

none

horizontal partitioning

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency per node, eventual consistency across nodes

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

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Access rights for users, groups and roles 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.