DBMS > 4D vs. BoltDB vs. Hazelcast vs. Heroic vs. RocksDB

System Properties Comparison 4D vs. BoltDB vs. Hazelcast vs. Heroic vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

An embedded key-value store for Go.

A widely adopted in-memory data grid

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

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

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

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

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

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

Website

www.4d.com

github.com/boltdb/bolt

hazelcast.com

github.com/spotify/heroic

rocksdb.org

Technical documentation

developer.4d.com

hazelcast.org/imdg/docs

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

Developer

4D, Inc

Hazelcast

Spotify

Facebook, Inc.

Initial release

1984

2013

2008

2014

2013

Current release

v20, April 2023

5.3.6, November 2023

8.11.4, April 2024

License

Commercial or Open Source

commercial

Open Source

MIT License

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

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

OS X
Windows

BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Linux

Data scheme

yes

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

via Elasticsearch

SQL

Support of SQL

yes

close to SQL 92

SQL-like query language

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JCache
JPA
Memcached protocol
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

C++ API
Java API

Supported programming languages

4D proprietary IDE
PHP

.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

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

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

Immediate Consistency

none

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

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

Users and groups

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.