DBMS > GeoMesa vs. Hazelcast vs. Ingres vs. MySQL vs. SpatiaLite

System Properties Comparison GeoMesa vs. Hazelcast vs. Ingres vs. MySQL vs. SpatiaLite

Editorial information provided by DB-Engines

Name

Description

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

A widely adopted in-memory data grid

Well established RDBMS

Widely used open source RDBMS

Spatial extension of SQLite

Primary database model

Spatial DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Spatial DBMS

Relational DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Website

www.geomesa.org

hazelcast.com

www.actian.com/databases/ingres

www.mysql.com

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

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

hazelcast.org/imdg/docs

docs.actian.com/ingres

dev.mysql.com/doc

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

CCRi and others

Hazelcast

Actian Corporation

Oracle

since 2010, originally MySQL AB, then Sun

Alessandro Furieri

Initial release

2014

2008

1974

originally developed at University Berkely in early 1970s

1995

2008

Current release

5.0.0, May 2024

5.3.6, November 2023

11.2, May 2022

8.4.0, April 2024

5.0.0, August 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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

C++

Server operating systems

All OS with a Java VM

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

server-less

Data scheme

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

the object must implement a serialization strategy

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

yes

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

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

Event Listeners, Executor Services

yes

proprietary syntax

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Replicated Map

Ingres Replicator

Multi-source replication
Source-replica replication

none

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 or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

one or two-phase-commit; repeatable reads; read commited

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

table locks or row locks depending on storage engine

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

Role-based access control

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.