DBMS > GeoMesa vs. Hazelcast vs. IBM Cloudant vs. KeyDB vs. MySQL

System Properties Comparison GeoMesa vs. Hazelcast vs. IBM Cloudant vs. KeyDB vs. MySQL

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

Database as a Service offering based on Apache CouchDB

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

www.geomesa.org

hazelcast.com

www.ibm.com/products/cloudant

github.com/Snapchat/KeyDB
keydb.dev

www.mysql.com

Technical documentation

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

hazelcast.org/imdg/docs

cloud.ibm.com/docs/Cloudant

docs.keydb.dev

dev.mysql.com/doc

Developer

CCRi and others

Hazelcast

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

EQ Alpha Technology Ltd.

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2014

2008

2010

2019

1995

Current release

4.0.5, February 2024

5.3.6, November 2023

8.3.0, January 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

BSD-3

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Cloud-based only

Only available as a cloud service

yes

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

Erlang

C++

C and C++

Server operating systems

All OS with a Java VM

hosted

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

yes

Secondary indexes

yes

by using the Redis Search module

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

RESTful HTTP/JSON API

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

C#
Java
JavaScript
Objective-C
PHP
Ruby

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

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

View functions (Map-Reduce) in JavaScript

Lua

yes

proprietary syntax

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Replicated Map

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

Raft Consensus Algorithm

Eventual Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

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

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

atomic operations within a document possible

Optimistic locking, atomic execution of commands blocks and scripts

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

Access rights for users can be defined per database

simple password-based access control and ACL

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.