DBMS > Badger vs. Hazelcast vs. RocksDB vs. VelocityDB

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

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)

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Key-value store

Graph DBMS
Object oriented 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	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.05
Rank	#358	Overall
	#36	Graph DBMS
	#16	Object oriented DBMS

Website

github.com/dgraph-io/badger

hazelcast.com

rocksdb.org

velocitydb.com

Technical documentation

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

hazelcast.org/imdg/docs

github.com/facebook/rocksdb/wiki

velocitydb.com/UserGuide

Developer

DGraph Labs

Hazelcast

Facebook, Inc.

VelocityDB Inc

Initial release

2017

2008

2013

2011

Current release

5.3.6, November 2023

8.11.4, April 2024

7.x

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

Open Source

BSD

commercial

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

All OS with a Java VM

Linux

Any that supports .NET

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

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

C++ API
Java API

.Net

Supported programming languages

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

C
C++
Go
Java
Perl
Python
Ruby

.Net

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

Triggers

yes

Events

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

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 or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

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

Based on Windows Authentication

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.