DBMS > BoltDB vs. etcd vs. Machbase Neo vs. RavenDB vs. RocksDB

System Properties Comparison BoltDB vs. etcd vs. Machbase Neo vs. RavenDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

A distributed reliable key-value store

TimeSeries DBMS for AIoT and BigData

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

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

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

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

Website

github.com/boltdb/bolt

etcd.io
github.com/etcd-io/etcd

machbase.com

ravendb.net

rocksdb.org

Technical documentation

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

machbase.com/dbms

ravendb.net/docs

github.com/facebook/rocksdb/wiki

Developer

Machbase

Hibernating Rhinos

Facebook, Inc.

Initial release

2013

2010

2013

Current release

3.4, August 2019

V8.0, August 2023

5.4, July 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2.0

commercial

free test version available

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++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
Windows

experimental

Linux
macOS
Windows

Linux
macOS
Raspberry Pi
Windows

Linux

Data scheme

schema-free

yes

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

SQL

Support of SQL

SQL-like query language

SQL-like query language (RQL)

APIs and other access methods

gRPC
JSON over HTTP

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

.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

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

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

selectable replication factor

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

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

yes

In-memory capabilities

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

yes

volatile and lookup table

yes

User concepts

Access control

simple password-based access control

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.