DBMS > GeoMesa vs. MarkLogic vs. Percona Server for MySQL vs. SAP HANA

System Properties Comparison GeoMesa vs. MarkLogic vs. Percona Server for MySQL vs. SAP HANA

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.

Operational and transactional Enterprise NoSQL database

Enhanced drop-in replacement for MySQL based on XtraDB or TokuDB storage engines with improved performance and additional diagnostic and management features.

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Spatial DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	5.18
Rank	#63	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#7	Search engines

Score	2.10
Rank	#119	Overall
	#57	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.geomesa.org

www.progress.com/marklogic

www.percona.com/software/mysql-database/percona-server

www.sap.com/products/hana.html

Technical documentation

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

www.progress.com/marklogic/documentation

www.percona.com/downloads/Percona-Server-LATEST

help.sap.com/hana

Developer

CCRi and others

MarkLogic Corp.

Percona

SAP

Initial release

2014

2001

2008

2010

Current release

5.0.0, May 2024

11.0, December 2022

8.0.36-28, 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

restricted free version is available

Open Source

GPL version 2

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

C++

C and C++

Server operating systems

Linux
OS X
Windows

Linux

Appliance or cloud-service

Data scheme

yes

schema-free

Schema can be enforced

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

SQL92

yes

APIs and other access methods

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

ADO.NET
JDBC
ODBC

JDBC
ODBC

Supported programming languages

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Ada
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

yes

SQLScript, R

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Multi-source replication
Source-replica replication
XtraDB Cluster

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

can act as a resource manager in an XA/JTA transaction

ACID

Concurrency

Support for concurrent manipulation of data

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, with Range Indexes

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Role-based access control at the document and subdocument levels

Users with fine-grained authorization concept

no user groups or roles

yes

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.