DBMS > GeoMesa vs. Graph Engine vs. H2 vs. MySQL

System Properties Comparison GeoMesa vs. Graph Engine vs. H2 vs. MySQL

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.

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Widely used open source RDBMS

Primary database model

Spatial DBMS

Graph DBMS
Key-value store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Spatial DBMS

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.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	8.33
Rank	#46	Overall
	#30	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Website

Technical documentation

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

www.graphengine.io/docs/manual

www.h2database.com/html/main.html

dev.mysql.com/doc

Developer

CCRi and others

Microsoft

Thomas Mueller

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2014

2010

2005

1995

Current release

5.0.0, May 2024

2.2.220, July 2023

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

MIT License

Open Source

dual-licence (Mozilla public license, Eclipse public license)

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

.NET and C

Java

C and C++

Server operating systems

.NET

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

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

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C#
C++
F#
Visual Basic

Java

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

Java Stored Procedures and User-Defined Functions

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

With clustering: 2 database servers on different computers operate on identical copies of a database

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

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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.