DBMS > Bangdb vs. etcd vs. Hazelcast vs. MySQL

System Properties Comparison Bangdb vs. etcd vs. Hazelcast vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Converged and high performance database for device data, events, time series, document and graph

A distributed reliable key-value store

A widely adopted in-memory data grid

Widely used open source RDBMS

Primary database model

Document store
Graph DBMS
Time Series DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Spatial DBMS

Document store

JSON support with IMDG 3.12

Document store
Spatial DBMS

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

Score	0.08
Rank	#347	Overall
	#47	Document stores
	#34	Graph DBMS
	#31	Time Series DBMS

Score	7.25
Rank	#54	Overall
	#5	Key-value stores

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

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

bangdb.com

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

hazelcast.com

www.mysql.com

Technical documentation

docs.bangdb.com

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

hazelcast.org/imdg/docs

dev.mysql.com/doc

Developer

Sachin Sinha, BangDB

Hazelcast

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

2008

1995

Current release

BangDB 2.0, October 2021

3.4, August 2019

5.3.6, November 2023

8.3.0, January 2024

License

Commercial or Open Source

Open Source

BSD 3

Open Source

Apache Version 2.0

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C, C++

Java

C and C++

Server operating systems

Linux

FreeBSD
Linux
Windows

experimental

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes: string, long, double, int, geospatial, stream, events

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

secondary, composite, nested, reverse, geospatial

yes

SQL

Support of SQL

SQL like support with command line tool

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

Proprietary protocol
RESTful HTTP API

gRPC
JSON over HTTP

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C#
C++
Java
Python

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

.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

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

proprietary syntax

Triggers

yes, Notifications (with Streaming only)

yes, watching key changes

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor, Knob for CAP (enterprise version only)

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

yes

Replicated Map

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable consistency, set CAP knob accordingly

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes, optimistic concurrency control

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes, implements WAL (Write ahead log) as well

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes, run db with in-memory only mode

yes

User concepts

Access control

yes (enterprise version only)

Role-based access control

Users with fine-grained authorization concept

no user groups or roles

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.