DBMS > GeoMesa vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Synapse Analytics vs. NSDb

System Properties Comparison GeoMesa vs. Microsoft Azure Cosmos DB vs. Microsoft Azure Synapse Analytics vs. NSDb

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

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

Primary database model

Spatial DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Time Series 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	20.56
Rank	#31	Overall
	#19	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Website

www.geomesa.org

azure.microsoft.com/services/cosmos-db

azure.microsoft.com/services/synapse-analytics

nsdb.io

Technical documentation

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

learn.microsoft.com/azure/cosmos-db

docs.microsoft.com/azure/synapse-analytics

nsdb.io/Architecture

Developer

CCRi and others

Microsoft

Initial release

2014

2016

2017

Current release

4.0.5, February 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache Version 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

C++

Java, Scala

Server operating systems

hosted

Linux
macOS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

yes

yes: int, bigint, decimal, string

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

yes

all fields are automatically indexed

SQL

Support of SQL

SQL-like query language

yes

SQL-like query language

APIs and other access methods

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

ADO.NET
JDBC
ODBC

gRPC
HTTP REST
WebSocket

Supported programming languages

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

C#
Java
PHP

Java
Scala

Server-side scripts

Stored procedures

JavaScript

Transact SQL

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Implicit feature of the cloud service

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Implicit feature of the cloud service

yes

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

Eventual Consistency

Foreign keys

Referential integrity

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights can be defined down to the item level

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.