DBMS > BoltDB vs. GeoSpock vs. Hazelcast vs. IRONdb vs. RocksDB

System Properties Comparison BoltDB vs. GeoSpock vs. Hazelcast vs. IRONdb vs. RocksDB

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

An embedded key-value store for Go.

Spatial and temporal data processing engine for extreme data scale

A widely adopted in-memory data grid

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

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

Primary database model

Secondary database models

Time Series DBMS

Document store

JSON support with IMDG 3.12

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

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

github.com/boltdb/bolt

geospock.com

hazelcast.com

www.circonus.com/solutions/time-series-database/

rocksdb.org

Technical documentation

hazelcast.org/imdg/docs

docs.circonus.com/irondb/category/getting-started

github.com/facebook/rocksdb/wiki

Developer

GeoSpock

Hazelcast

Circonus LLC.

Facebook, Inc.

Initial release

2013

2008

2017

2013

Current release

2.0, September 2019

5.3.6, November 2023

V0.10.20, January 2018

9.2.1, May 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

BSD

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Javascript

Java

C and C++

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

All OS with a Java VM

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language

SQL-like query language (Circonus Analytics Query Language: CAQL)

APIs and other access methods

JDBC

JCache
JPA
Memcached protocol
RESTful HTTP API

HTTP API

C++ API
Java API

Supported programming languages

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

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes, in Lua

Triggers

yes

Events

Partitioning methods

Methods for storing different data on different nodes

none

Automatic sharding

Sharding

Automatic, metric affinity per node

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Replicated Map

configurable replication factor, datacenter aware

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

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate consistency per node, eventual consistency across nodes

Foreign keys

Referential integrity

Transaction concepts

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

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

Access rights for users can be defined per table

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.