DBMS > BoltDB vs. Heroic vs. Oracle Berkeley DB vs. RocksDB vs. Sequoiadb

System Properties Comparison BoltDB vs. Heroic vs. Oracle Berkeley DB vs. RocksDB vs. Sequoiadb

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

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

Widely used in-process key-value store

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

NewSQL database with distributed OLTP and SQL

Primary database model

Key-value store

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

Document store
Relational DBMS

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

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

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

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

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Website

github.com/boltdb/bolt

github.com/spotify/heroic

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

rocksdb.org

www.sequoiadb.com

Technical documentation

spotify.github.io/heroic

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

github.com/facebook/rocksdb/wiki

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Spotify

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Facebook, Inc.

Sequoiadb Ltd.

Initial release

2013

2014

1994

2013

Current release

18.1.40, May 2020

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

Open Source

commercial license available

Open Source

BSD

Open Source

Server: AGPL; Client: Apache V2

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

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

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

via Elasticsearch

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

SQL-like query language

APIs and other access methods

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

C++ API
Java API

proprietary protocol using JSON

Supported programming languages

.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

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

JavaScript

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Source-replica replication

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

ACID

yes

Document is locked during a transaction

Concurrency

Support for concurrent manipulation of data

yes

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

simple password-based access control

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.