DBMS > BoltDB vs. GeoMesa vs. HBase vs. RocksDB vs. Stardog

System Properties Comparison BoltDB vs. GeoMesa vs. HBase vs. RocksDB vs. Stardog

Editorial information provided by DB-Engines

Name

Description

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

Wide-column store based on Apache Hadoop and on concepts of BigTable

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

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

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

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

github.com/boltdb/bolt

Technical documentation

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

hbase.apache.org/book.html

github.com/facebook/rocksdb/wiki

docs.stardog.com

Developer

CCRi and others

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Facebook, Inc.

Stardog-Union

Initial release

2013

2014

2008

2013

2010

Current release

5.0.0, May 2024

2.3.4, January 2021

9.2.1, May 2024

7.3.0, May 2020

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache License 2.0

Open Source

Apache version 2

Open Source

BSD

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
Unix
Windows

using Cygwin

Linux

Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free, schema definition possible

schema-free

schema-free and OWL/RDFS-schema support

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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.

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

Java API
RESTful HTTP API
Thrift

C++ API
Java API

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

C
C++
Go
Java
Perl
Python
Ruby

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

yes

Coprocessors in Java

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

Multi-source replication
Source-replica replication

yes

Multi-source replication in HA-Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

depending on storage layer

Immediate Consistency or Eventual Consistency

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

yes

relationships in graphs

Transaction concepts

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

yes

Single row ACID (across millions of columns)

yes

ACID

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

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

Access rights for users and roles

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.