DBMS > GeoMesa vs. Microsoft Azure SQL Database vs. SAP HANA vs. TigerGraph

System Properties Comparison GeoMesa vs. Microsoft Azure SQL Database vs. SAP HANA vs. TigerGraph

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.

Database as a Service offering with high compatibility to Microsoft SQL Server

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

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Spatial DBMS

Relational DBMS

Graph DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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	76.78
Rank	#16	Overall
	#11	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

www.geomesa.org

azure.microsoft.com/en-us/products/azure-sql/database

www.sap.com/products/hana.html

www.tigergraph.com

Technical documentation

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

docs.microsoft.com/en-us/azure/azure-sql

help.sap.com/hana

docs.tigergraph.com

Developer

CCRi and others

Microsoft

SAP

Initial release

2014

2010

2017

Current release

5.0.0, May 2024

V12

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

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

C++

Server operating systems

hosted

Appliance or cloud-service

Linux

Data scheme

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

SQL-like query language (GSQL)

APIs and other access methods

ADO.NET
JDBC
ODBC

JDBC
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

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

C++
Java

Server-side scripts

Stored procedures

Transact SQL

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

yes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes, with always 3 replicas available

yes

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

Foreign keys

Referential integrity

yes

Relationships in graphs

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

yes

Role-based access control

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.