DBMS > Badger vs. Hazelcast vs. RocksDB vs. TerminusDB

System Properties Comparison Badger vs. Hazelcast vs. RocksDB vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

A widely adopted in-memory data grid

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Key-value store

Graph DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
RDF store

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

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

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

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

github.com/dgraph-io/badger

hazelcast.com

rocksdb.org

terminusdb.com

Technical documentation

godoc.org/github.com/dgraph-io/badger

hazelcast.org/imdg/docs

github.com/facebook/rocksdb/wiki

terminusdb.github.io/terminusdb/#

Developer

DGraph Labs

Hazelcast

Facebook, Inc.

DataChemist Ltd.

Initial release

2017

2008

2013

2018

Current release

5.3.6, November 2023

8.11.4, April 2024

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Linux

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

SQL-like query language (WOQL)

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

C++ API
Java API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

JavaScript
Python

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Replicated Map

yes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

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.