DBMS > GeoMesa vs. Heroic vs. IBM Db2 Event Store vs. LokiJS vs. MySQL

System Properties Comparison GeoMesa vs. Heroic vs. IBM Db2 Event Store vs. LokiJS vs. MySQL

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

Distributed Event Store optimized for Internet of Things use cases

In-memory JavaScript DBMS

Widely used open source RDBMS

Primary database model

Spatial DBMS

Time Series DBMS

Event Store
Time Series DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	0.27
Rank	#309	Overall
	#2	Event Stores
	#28	Time Series DBMS

Score	0.49
Rank	#260	Overall
	#42	Document stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

www.geomesa.org

github.com/spotify/heroic

www.ibm.com/products/db2-event-store

github.com/techfort/LokiJS

www.mysql.com

Technical documentation

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

spotify.github.io/heroic

www.ibm.com/docs/en/db2-event-store

techfort.github.io/LokiJS

dev.mysql.com/doc

Developer

CCRi and others

Spotify

IBM

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2014

2017

2014

1995

Current release

5.0.0, May 2024

2.0

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

commercial

free developer edition available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Scala

Java

C and C++

JavaScript

C and C++

Server operating systems

Linux

Linux, macOS, Windows for the developer addition

server-less, requires a JavaScript environment (browser, Node.js)

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

schema-free

yes

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.

yes

Secondary indexes

yes

via Elasticsearch

yes

via views

yes

SQL

Support of SQL

yes

through the embedded Spark runtime

yes

with proprietary extensions

APIs and other access methods

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

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

JavaScript API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

JavaScript

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

View functions in JavaScript

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Active-active shard replication

none

Multi-source replication
Source-replica replication

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

Eventual Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

atomic operations within a single collection possible

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

No - written data is immutable

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or 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.