DBMS > GeoMesa vs. MySQL vs. Oracle Rdb vs. Percona Server for MongoDB

System Properties Comparison GeoMesa vs. MySQL vs. Oracle Rdb vs. Percona Server for MongoDB

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.

Widely used open source RDBMS

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Spatial DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Document store

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	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.14
Rank	#178	Overall
	#80	Relational DBMS

Score	0.60
Rank	#246	Overall
	#39	Document stores

Website

www.geomesa.org

www.mysql.com

www.oracle.com/database/technologies/related/rdb.html

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

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

dev.mysql.com/doc

www.oracle.com/database/technologies/related/rdb-doc.html

docs.percona.com/percona-distribution-for-mongodb

Developer

CCRi and others

Oracle

since 2010, originally MySQL AB, then Sun

Oracle, originally developed by Digital Equipment Corporation (DEC)

Percona

Initial release

2014

1995

1984

2015

Current release

5.0.0, May 2024

8.4.0, April 2024

7.4.1.1, 2021

3.4.10-2.10, November 2017

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

GPL Version 2

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

C++

Server operating systems

FreeBSD
Linux
OS X
Solaris
Windows

HP Open VMS

Linux

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

schema-free

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

yes

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

proprietary protocol using JSON

Supported programming languages

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

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

yes

proprietary syntax

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

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

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

Eventual Consistency
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

ACID

not for MyISAM storage engine

yes, on a single node

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

yes

via In-Memory Engine

User concepts

Access control

yes

depending on the DBMS used for storage

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and 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.