DBMS > Datomic vs. GeoMesa vs. HEAVY.AI vs. Riak KV vs. RocksDB

System Properties Comparison Datomic vs. GeoMesa vs. HEAVY.AI vs. Riak KV vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Distributed, fault tolerant key-value store

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

Primary database model

with links between data sets and object tags for the creation of secondary indexes

Key-value store

Secondary database models

Spatial DBMS

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

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

Website

www.datomic.com

www.geomesa.org

github.com/heavyai/heavydb
www.heavy.ai

rocksdb.org

Technical documentation

docs.datomic.com

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

docs.heavy.ai

www.tiot.jp/riak-docs/riak/kv/latest

github.com/facebook/rocksdb/wiki

Developer

Cognitect

CCRi and others

HEAVY.AI, Inc.

OpenSource, formerly Basho Technologies

Facebook, Inc.

Initial release

2012

2014

2016

2009

2013

Current release

1.0.7075, December 2023

5.0.0, May 2024

5.10, January 2022

3.2.0, December 2022

9.2.1, May 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache License 2.0

Open Source

Apache Version 2; enterprise edition available

Open Source

Apache version 2, commercial enterprise edition

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, Clojure

Scala

C++ and CUDA

Erlang

C++

Server operating systems

All OS with a Java VM

Linux

Linux
OS X

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

restricted

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

JDBC
ODBC
Thrift
Vega

HTTP API
Native Erlang Interface

C++ API
Java API

Supported programming languages

Clojure
Java

All languages supporting JDBC/ODBC/Thrift
Python

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Transaction Functions

Erlang

Triggers

By using transaction functions

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

depending on storage layer

Sharding

Round robin

Sharding

no "single point of failure"

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

depending on storage layer

Multi-source replication

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

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

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

yes, using Riak Security

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.