DBMS > EXASOL vs. GeoMesa vs. MarkLogic vs. SAP HANA vs. SQream DB

System Properties Comparison EXASOL vs. GeoMesa vs. MarkLogic vs. SAP HANA vs. SQream DB

Editorial information provided by DB-Engines

Name

Description

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

Operational and transactional Enterprise NoSQL database

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

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Relational DBMS

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	1.76
Rank	#139	Overall
	#62	Relational DBMS

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	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.74
Rank	#224	Overall
	#103	Relational DBMS

Website

www.exasol.com

www.geomesa.org

www.marklogic.com

www.sap.com/products/hana.html

sqream.com

Technical documentation

www.exasol.com/resources

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

docs.marklogic.com

help.sap.com/hana

docs.sqream.com

Developer

Exasol

CCRi and others

MarkLogic Corp.

SAP

SQream Technologies

Initial release

2000

2014

2001

2010

2017

Current release

5.0.0, May 2024

11.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

2022.1.6, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

restricted free version is available

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++, CUDA, Haskell, Java, Scala

Server operating systems

Linux
OS X
Windows

Appliance or cloud-service

Linux

Data scheme

yes

schema-free

Schema can be enforced

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

.Net
JDBC
ODBC
WebSocket

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

JDBC
ODBC

.Net
JDBC
ODBC

Supported programming languages

Java
Lua
Python
R

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

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

via XQuery or JavaScript

SQLScript, R

user defined functions in Python

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

yes

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

yes

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

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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.

yes

depending on storage layer

yes, with Range Indexes

yes

User concepts

Access control

Access rights for users, groups and roles according to SQL-standard

yes

depending on the DBMS used for storage

Role-based access control at the document and subdocument levels

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.