DBMS > Badger vs. Hazelcast vs. MySQL vs. TerminusDB

System Properties Comparison Badger vs. Hazelcast vs. MySQL 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

Widely used open source RDBMS

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

Primary database model

Key-value store

Relational DBMS

Key/Value like access via memcached API

Graph DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Spatial DBMS

Document store
RDF store

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

Score	0.14
Rank	#328	Overall
	#48	Key-value stores

Score	5.72
Rank	#59	Overall
	#6	Key-value stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.19
Rank	#311	Overall
	#27	Graph DBMS

Website

github.com/dgraph-io/badger

hazelcast.com

www.mysql.com

terminusdb.com

Technical documentation

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

hazelcast.org/imdg/docs

dev.mysql.com/doc

terminusdb.github.io/terminusdb/#

Developer

DGraph Labs

Hazelcast

Oracle

since 2010, originally MySQL AB, then Sun

DataChemist Ltd.

Initial release

2017

2008

1995

2018

Current release

5.3.6, November 2023

9.0.0, July 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

GPL version 2. Commercial licenses with extended functionallity are available

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

Prolog, Rust

Server operating systems

BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

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

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

SQL-like query language (WOQL)

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript
Python

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

proprietary syntax

yes

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Replicated Map

Multi-source replication
Source-replica replication

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

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

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.