DBMS > GeoMesa vs. H2GIS vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. TinkerGraph

System Properties Comparison GeoMesa vs. H2GIS vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Table Storage vs. TinkerGraph

Editorial information provided by DB-Engines

Name

Description

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

Spatial extension of H2

Globally distributed, horizontally scalable, multi-model database service

A Wide Column Store for rapid development using massive semi-structured datasets

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Spatial DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Wide column store

Graph DBMS

Secondary database models

Relational DBMS

Spatial DBMS

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

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.05
Rank	#372	Overall
	#7	Spatial DBMS

Score	29.85
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	4.92
Rank	#73	Overall
	#6	Wide column stores

Score	0.12
Rank	#344	Overall
	#34	Graph DBMS

Website

www.geomesa.org

www.h2gis.org

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/en-us/services/storage/tables

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

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

www.h2gis.org/docs/home

learn.microsoft.com/azure/cosmos-db

Developer

CCRi and others

CNRS

Microsoft

Initial release

2014

2013

2014

2012

2009

Current release

4.0.5, February 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

LGPL 3.0

commercial

Open Source

Apache 2.0

Cloud-based only

Only available as a cloud service

yes

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

hosted

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON 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.

Secondary indexes

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

RESTful HTTP API

TinkerPop 3

Supported programming languages

Java

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

Groovy
Java

Server-side scripts

Stored procedures

yes

based on H2

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

Implicit feature of the cloud service

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

based on H2

yes

Implicit feature of the cloud service

yes

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

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

optional

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

yes

based on H2

Access rights can be defined down to the item level

Access rights based on private key authentication or shared access signatures

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.