DBMS > etcd vs. HBase vs. Heroic vs. RocksDB vs. VoltDB

System Properties Comparison etcd vs. HBase vs. Heroic vs. RocksDB vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

A distributed reliable key-value store

Wide-column store based on Apache Hadoop and on concepts of BigTable

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

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

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

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

Score	31.25
Rank	#26	Overall
	#2	Wide column stores

Score	0.57
Rank	#250	Overall
	#21	Time Series DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Score	1.46
Rank	#159	Overall
	#74	Relational DBMS

Website

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

hbase.apache.org

github.com/spotify/heroic

rocksdb.org

www.voltdb.com

Technical documentation

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

hbase.apache.org/book.html

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

docs.voltdb.com

Developer

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Spotify

Facebook, Inc.

VoltDB Inc.

Initial release

2008

2014

2013

2010

Current release

3.4, August 2019

2.3.4, January 2021

8.11.4, April 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache version 2

Open Source

Apache 2.0

Open Source

BSD

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Server operating systems

FreeBSD
Linux
Windows

experimental

Linux
Unix
Windows

using Cygwin

Linux

Linux
OS X

for development

Data scheme

schema-free

schema-free, schema definition possible

schema-free

yes

Typing

predefined data types such as float or date

options to bring your own types, AVRO

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

yes

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

gRPC
JSON over HTTP

Java API
RESTful HTTP API
Thrift

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

C++ API
Java API

Java API
JDBC
RESTful HTTP/JSON 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++
Groovy
Java
PHP
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Coprocessors in Java

Java

Triggers

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

FOREIGN KEY constraints are not supported

Transaction concepts

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

Single row ACID (across millions of columns)

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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 Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

Users and roles with access to stored procedures

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.