DBMS > Hazelcast vs. Prometheus vs. RavenDB vs. RocksDB vs. Transbase

System Properties Comparison Hazelcast vs. Prometheus vs. RavenDB vs. RocksDB vs. Transbase

Editorial information provided by DB-Engines

Name

Description

A widely adopted in-memory data grid

Open-source Time Series DBMS and monitoring system

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Graph DBMS
Spatial DBMS
Time Series DBMS

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

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

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

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

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

www.transaction.de/en/products/transbase.html

Technical documentation

hazelcast.org/imdg/docs

prometheus.io/docs

ravendb.net/docs

github.com/facebook/rocksdb/wiki

www.transaction.de/en/products/transbase/features.html

Developer

Hazelcast

Hibernating Rhinos

Facebook, Inc.

Transaction Software GmbH

Initial release

2008

2015

2010

2013

1987

Current release

5.3.6, November 2023

5.4, July 2022

8.11.4, April 2024

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

Open Source

AGPL version 3, commercial license available

Open Source

BSD

commercial

free development license

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++

C and C++

Server operating systems

All OS with a Java VM

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

SQL-like query language (RQL)

yes

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

RESTful HTTP/JSON API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

C++ API
Java API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

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

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes

by Federation

Multi-source replication

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

none

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

ACID, Cluster-wide transaction available

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

Role-based access control

Authorization levels configured per client per database

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.