DBMS > etcd vs. Hazelcast vs. RocksDB vs. TimesTen vs. VoltDB

System Properties Comparison etcd vs. Hazelcast vs. RocksDB vs. TimesTen vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

A distributed reliable key-value store

A widely adopted in-memory data grid

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

In-Memory RDBMS compatible to Oracle

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

Key-value store

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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

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

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

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

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

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

hazelcast.com

rocksdb.org

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

www.voltdb.com

Technical documentation

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

hazelcast.org/imdg/docs

github.com/facebook/rocksdb/wiki

docs.oracle.com/database/timesten-18.1

docs.voltdb.com

Developer

Hazelcast

Facebook, Inc.

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

VoltDB Inc.

Initial release

2008

2013

1998

2010

Current release

3.4, August 2019

5.3.6, November 2023

9.2.1, May 2024

11 Release 2 (11.2.2.8.0)

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD

commercial

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

All OS with a Java VM

Linux

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
OS X

for development

Data scheme

schema-free

yes

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.

yes

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

only a subset of SQL 99

APIs and other access methods

gRPC
JSON over HTTP

JCache
JPA
Memcached protocol
RESTful HTTP API

C++ API
Java API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

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

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

C
C++
Java
PL/SQL

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

PL/SQL

Java

Triggers

yes, watching key changes

yes

Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

none

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.

yes

Replicated Map

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 selectable by user

Raft Consensus Algorithm

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

one or two-phase-commit; repeatable reads; read commited

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

by means of logfiles and checkpoints

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

Role-based access control

fine grained access rights according to SQL-standard

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.