DBMS > GeoMesa vs. KeyDB vs. mSQL vs. MySQL vs. Prometheus

System Properties Comparison GeoMesa vs. KeyDB vs. mSQL vs. MySQL vs. Prometheus

Editorial information provided by DB-Engines

Name

Description

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

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

Widely used open source RDBMS

Open-source Time Series DBMS and monitoring system

Primary database model

Spatial DBMS

Key-value store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

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	0.71
Rank	#226	Overall
	#33	Key-value stores

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Website

www.geomesa.org

github.com/Snapchat/KeyDB
keydb.dev

hughestech.com.au/products/msql

www.mysql.com

prometheus.io

Technical documentation

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

docs.keydb.dev

dev.mysql.com/doc

prometheus.io/docs

Developer

CCRi and others

EQ Alpha Technology Ltd.

Hughes Technologies

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2014

2019

1994

1995

2015

Current release

4.0.5, February 2024

4.4, October 2021

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

BSD-3

commercial

free licenses can be provided

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

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

C++

C and C++

Server operating systems

Linux

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
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

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

by using the Redis Search module

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

with proprietary extensions

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP/JSON API

Supported programming languages

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

C
C++
Delphi
Java
Perl
PHP
Tcl

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

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

Server-side scripts

Stored procedures

Lua

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication
Source-replica replication

none

Multi-source replication
Source-replica replication

yes

by Federation

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
Strong eventual consistency with CRDTs

none

Immediate Consistency

none

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

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

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.