DBMS > Apache Drill vs. BoltDB vs. IRONdb vs. RavenDB vs. RocksDB

System Properties Comparison Apache Drill vs. BoltDB vs. IRONdb vs. RavenDB vs. RocksDB

Editorial information provided by DB-Engines

Name

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

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

An embedded key-value store for Go.

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Primary database model

Document store
Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	2.84
Rank	#101	Overall
	#18	Document stores

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

Website

drill.apache.org

github.com/boltdb/bolt

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

ravendb.net

rocksdb.org

Technical documentation

drill.apache.org/docs

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

ravendb.net/docs

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Circonus LLC.

Hibernating Rhinos

Facebook, Inc.

Initial release

2012

2013

2017

2010

2013

Current release

1.20.3, January 2023

V0.10.20, January 2018

5.4, July 2022

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

MIT License

commercial

Open Source

AGPL version 3, commercial license available

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

C and C++

C++

Server operating systems

Linux
OS X
Windows

BSD
Linux
OS X
Solaris
Windows

Linux

Linux
macOS
Raspberry Pi
Windows

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

SQL SELECT statement is SQL:2003 compliant

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

SQL-like query language (RQL)

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

HTTP API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

C++ API
Java API

Supported programming languages

C++

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

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes, in Lua

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Automatic, metric affinity per node

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

configurable replication factor, datacenter aware

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate consistency per node, eventual consistency across nodes

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

Transaction concepts

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

yes

ACID, Cluster-wide transaction available

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

Authorization levels configured per client per database

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.