DBMS > GeoMesa vs. Greenplum vs. Microsoft Azure Data Explorer vs. OrientDB vs. SAP HANA

System Properties Comparison GeoMesa vs. Greenplum vs. Microsoft Azure Data Explorer vs. OrientDB vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

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

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

Fully managed big data interactive analytics platform

Multi-model DBMS (Document, Graph, Key/Value)

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

Primary database model

Spatial DBMS

Relational DBMS

column oriented

Document store
Graph DBMS
Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	4.38
Rank	#77	Overall
	#41	Relational DBMS

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Website

www.geomesa.org

greenplum.org

azure.microsoft.com/services/data-explorer

orientdb.org

www.sap.com/products/hana.html

Technical documentation

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

docs.greenplum.org

docs.microsoft.com/en-us/azure/data-explorer

www.orientdb.com/docs/last/index.html

help.sap.com/hana

Developer

CCRi and others

Pivotal Software Inc.

Microsoft

OrientDB LTD; CallidusCloud; SAP

SAP

Initial release

2014

2005

2019

2010

Current release

5.0.0, May 2024

7.0.0, September 2023

cloud service with continuous releases

3.2.29, March 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

commercial

Open Source

Apache version 2

commercial

Cloud-based only

Only available as a cloud service

yes

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

Java

Server operating systems

Linux

hosted

All OS with a Java JDK (>= JDK 6)

Appliance or cloud-service

Data scheme

yes

Fixed schema with schema-less datatypes (dynamic)

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

Typing

predefined data types such as float or date

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

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

since Version 4.2

yes

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

Kusto Query Language (KQL), SQL subset

SQL-like query language, no joins

yes

APIs and other access methods

JDBC
ODBC

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

JDBC
ODBC

Supported programming languages

C
Java
Perl
Python
R

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

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

Server-side scripts

Stored procedures

yes

Yes, possible languages: KQL, Python, R

Java, Javascript

SQLScript, R

Triggers

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

Hooks

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Implicit feature of the cloud service

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Spark connector (open source): github.com/Azure/azure-kusto-spark

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

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

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Azure Active Directory Authentication

Access rights for users and roles; record level security configurable

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.