DBMS > BoltDB vs. Hazelcast vs. Ingres vs. RocksDB

System Properties Comparison BoltDB vs. Hazelcast vs. Ingres vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

A widely adopted in-memory data grid

Well established RDBMS

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

Primary database model

Key-value store

Relational DBMS

Key-value store

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.76
Rank	#224	Overall
	#32	Key-value stores

Score	6.87
Rank	#55	Overall
	#6	Key-value stores

Score	4.67
Rank	#77	Overall
	#42	Relational DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Website

github.com/boltdb/bolt

hazelcast.com

www.actian.com/databases/ingres

rocksdb.org

Technical documentation

hazelcast.org/imdg/docs

docs.actian.com/ingres

github.com/facebook/rocksdb/wiki

Developer

Hazelcast

Actian Corporation

Facebook, Inc.

Initial release

2013

2008

1974

originally developed at University Berkely in early 1970s

2013

Current release

5.3.6, November 2023

11.2, May 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache Version 2; commercial licenses available

commercial

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

BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux

Data scheme

schema-free

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

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

C++ API
Java API

Supported programming languages

.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

yes

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Replicated Map

Ingres Replicator

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

yes

Transaction concepts

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

yes

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

MVCC

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

fine grained access rights according to SQL-standard

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.