DBMS > Badger vs. Dgraph vs. Hazelcast vs. RocksDB

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

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.

Distributed and scalable native Graph DBMS

A widely adopted in-memory data grid

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

Primary database model

Key-value store

Graph DBMS

Key-value store

Secondary database models

Document store

JSON support with IMDG 3.12

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

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

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

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

Website

github.com/dgraph-io/badger

dgraph.io

hazelcast.com

rocksdb.org

Technical documentation

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

dgraph.io/docs

hazelcast.org/imdg/docs

github.com/facebook/rocksdb/wiki

Developer

DGraph Labs

Dgraph Labs, Inc.

Hazelcast

Facebook, Inc.

Initial release

2017

2016

2008

2013

Current release

5.3.6, November 2023

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses 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

Java

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

All OS with a Java VM

Linux

Data scheme

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.

yes

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

C++ API
Java API

Supported programming languages

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

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

Triggers

yes

Events

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication via Raft

yes

Replicated Map

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

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Foreign keys

Referential integrity

Transaction concepts

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

ACID

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

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

Planned for future releases

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.