DBMS > GeoMesa vs. Microsoft Azure Cosmos DB vs. Stardog vs. Transbase

System Properties Comparison GeoMesa vs. Microsoft Azure Cosmos DB vs. Stardog vs. Transbase

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.

Globally distributed, horizontally scalable, multi-model database service

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Spatial DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Graph DBMS
RDF store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

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

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Score	0.11
Rank	#341	Overall
	#150	Relational DBMS

Website

www.geomesa.org

azure.microsoft.com/services/cosmos-db

www.stardog.com

www.transaction.de/en/products/transbase.html

Technical documentation

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

learn.microsoft.com/azure/cosmos-db

docs.stardog.com

www.transaction.de/en/products/transbase/features.html

Developer

CCRi and others

Microsoft

Stardog-Union

Transaction Software GmbH

Initial release

2014

2010

1987

Current release

4.0.5, February 2024

7.3.0, May 2020

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

commercial

free development license

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

C and C++

Server operating systems

hosted

Linux
macOS
Windows

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

schema-free and OWL/RDFS-schema support

yes

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.

Import/export of XML data possible

Secondary indexes

yes

All properties auto-indexed by default

yes

supports real-time indexing in full-text and geospatial

yes

SQL

Support of SQL

SQL-like query language

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

yes

APIs and other access methods

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

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

JavaScript

user defined functions and aggregates, HTTP Server extensions in Java

yes

Triggers

JavaScript

yes

via event handlers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Implicit feature of the cloud service

Multi-source replication in HA-Cluster

Source-replica replication

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency in HA-Cluster

Immediate Consistency

Foreign keys

Referential integrity

yes

relationships in graphs

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

yes

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

Access rights can be defined down to the item level

Access rights for users and roles

fine grained access rights according to SQL-standard

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.