DBMS > Prometheus vs. RavenDB vs. RocksDB vs. Transbase vs. Transwarp Hippo

System Properties Comparison Prometheus vs. RavenDB vs. RocksDB vs. Transbase vs. Transwarp Hippo

Editorial information provided by DB-Engines

Name

Description

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

Cloud-native distributed Vector DBMS that supports storage, retrieval, and management of massive vector-based datasets

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

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

Score	0.00
Rank	#383	Overall
	#13	Vector DBMS

Website

prometheus.io

ravendb.net

rocksdb.org

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

www.transwarp.cn/en/subproduct/hippo

Technical documentation

prometheus.io/docs

ravendb.net/docs

github.com/facebook/rocksdb/wiki

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

Developer

Hibernating Rhinos

Facebook, Inc.

Transaction Software GmbH

Initial release

2015

2010

2013

1987

2023

Current release

5.4, July 2022

8.11.4, April 2024

Transbase 8.3, 2022

1.0, May 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

AGPL version 3, commercial license available

Open Source

BSD

commercial

free development license

commercial

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

C++

C and C++

C++

Server operating systems

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Linux

FreeBSD
Linux
macOS
Solaris
Windows

Linux
macOS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

Numeric data only

yes

Vector, Numeric and String

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.

Import of XML data possible

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (RQL)

yes

APIs and other access methods

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

RESTful HTTP API

Supported programming languages

.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

C++
Java
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

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

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

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

Authorization levels configured per client per database

fine grained access rights according to SQL-standard

Role based access control and fine grained access rights

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.