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

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

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

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)

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	1.99
Rank	#133	Overall
	#23	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

Website

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

geode.apache.org

hbase.apache.org

github.com/spotify/heroic

rocksdb.org

Technical documentation

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

geode.apache.org/docs

hbase.apache.org/book.html

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Spotify

Facebook, Inc.

Initial release

2002

2008

2014

2013

Current release

3.4, August 2019

1.1, February 2017

2.3.4, January 2021

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache version 2

Open Source

Apache 2.0

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

C++

Server operating systems

FreeBSD
Linux
Windows

experimental

All OS with a Java VM

the JDK (8 or later) is also required

Linux
Unix
Windows

using Cygwin

Linux

Data scheme

schema-free

schema-free, schema definition possible

schema-free

Typing

predefined data types such as float or date

yes

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

SQL

Support of SQL

SQL-like query language (OQL)

APIs and other access methods

gRPC
JSON over HTTP

Java Client API
Memcached protocol
RESTful HTTP API

Java API
RESTful HTTP API
Thrift

HQL (Heroic Query Language, a JSON-based language)
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

.Net
All JVM based languages
C++
Groovy
Java
Scala

C
C#
C++
Groovy
Java
PHP
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Coprocessors in Java

Triggers

yes, watching key changes

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

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

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency or Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes, on a single node

Single row ACID (across millions of columns)

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

User concepts

Access control

Access rights per client and object definable

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.