DBMS > GeoMesa vs. Heroic vs. Immudb vs. RocksDB

System Properties Comparison GeoMesa vs. Heroic vs. Immudb vs. RocksDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

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

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

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

Primary database model

Spatial DBMS

Time Series DBMS

Key-value store

Secondary database models

Relational DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.24
Rank	#305	Overall
	#43	Key-value stores

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

Website

www.geomesa.org

github.com/spotify/heroic

github.com/codenotary/immudb
immudb.io

rocksdb.org

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

spotify.github.io/heroic

docs.immudb.io

github.com/facebook/rocksdb/wiki

Developer

CCRi and others

Spotify

Codenotary

Facebook, Inc.

Initial release

2014

2020

2013

Current release

4.0.5, February 2024

1.2.3, April 2022

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

Apache Version 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

Scala

Java

C++

Server operating systems

BSD
Linux
macOS
Solaris
Windows
z/OS

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.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

SQL-like syntax

APIs and other access methods

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

gRPC protocol
PostgreSQL wire protocol

C++ API
Java API

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
Python

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

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.

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

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.