DBMS > Apache Drill vs. BoltDB vs. Heroic vs. Riak KV vs. RocksDB

System Properties Comparison Apache Drill vs. BoltDB vs. Heroic vs. Riak KV vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

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

An embedded key-value store for Go.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Distributed, fault tolerant key-value store

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

Primary database model

Document store
Relational DBMS

Key-value store

Time Series DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Key-value store

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

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

Website

drill.apache.org

github.com/boltdb/bolt

github.com/spotify/heroic

rocksdb.org

Technical documentation

drill.apache.org/docs

spotify.github.io/heroic

www.tiot.jp/riak-docs/riak/kv/latest

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Spotify

OpenSource, formerly Basho Technologies

Facebook, Inc.

Initial release

2012

2013

2014

2009

2013

Current release

1.20.3, January 2023

3.2.0, December 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

MIT License

Open Source

Apache 2.0

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

C++

Server operating systems

Linux
OS X
Windows

BSD
Linux
OS X
Solaris
Windows

Linux
OS X

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

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

via Elasticsearch

restricted

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

HTTP API
Native Erlang Interface

C++ API
Java API

Supported programming languages

C++

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

no "single point of failure"

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

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

yes, using Riak Security

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.