DBMS > BoltDB vs. Hazelcast vs. HBase vs. RocksDB vs. Vitess

System Properties Comparison BoltDB vs. Hazelcast vs. HBase vs. RocksDB vs. Vitess

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

A widely adopted in-memory data grid

Wide-column store based on Apache Hadoop and on concepts of BigTable

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

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.74
Rank	#220	Overall
	#31	Key-value stores

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

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

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

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

github.com/boltdb/bolt

Technical documentation

hazelcast.org/imdg/docs

hbase.apache.org/book.html

github.com/facebook/rocksdb/wiki

vitess.io/docs

Developer

Hazelcast

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Facebook, Inc.

The Linux Foundation, PlanetScale

Initial release

2013

2008

2013

Current release

5.3.6, November 2023

2.3.4, January 2021

8.11.4, April 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache version 2

Open Source

BSD

Open Source

Apache Version 2.0, commercial licenses 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.

Implementation language

Java

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Linux
Unix
Windows

using Cygwin

Linux

Docker
Linux
macOS

Data scheme

schema-free

schema-free, schema definition possible

schema-free

yes

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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

yes

with proprietary extensions

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

Java API
RESTful HTTP API
Thrift

C++ API
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

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

C
C#
C++
Groovy
Java
PHP
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

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

Coprocessors in Java

yes

proprietary syntax

Triggers

yes

Events

yes

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

Multi-source replication
Source-replica replication

yes

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

none

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency or Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

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

Single row ACID (across millions of columns)

yes

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

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.