DBMS > GeoMesa vs. Google Cloud Datastore vs. Microsoft Azure Synapse Analytics vs. NSDb

System Properties Comparison GeoMesa vs. Google Cloud Datastore 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.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

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

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	22.71
Rank	#30	Overall
	#18	Relational DBMS

Score	0.00
Rank	#396	Overall
	#42	Time Series DBMS

Website

www.geomesa.org

cloud.google.com/datastore

azure.microsoft.com/services/synapse-analytics

nsdb.io

Technical documentation

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

cloud.google.com/datastore/docs

docs.microsoft.com/azure/synapse-analytics

nsdb.io/Architecture

Developer

CCRi and others

Google

Microsoft

Initial release

2014

2008

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

yes, details here

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 fields are automatically indexed

SQL

Support of SQL

SQL-like query language (GQL)

yes

SQL-like query language

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

gRPC
HTTP REST
WebSocket

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
Java
PHP

Java
Scala

Server-side scripts

Stored procedures

using Google App Engine

Transact SQL

Triggers

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication using Paxos

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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 for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Best cloud storage of 2024
3 April 2024, TechRadar

What Is Google Cloud Platform?
28 August 2023, Simplilearn

Compare Google Cloud Storage vs. Google Drive for enterprises
9 November 2023, TechTarget

provided by Google News

Migrate Microsoft Azure Synapse Analytics to Amazon Redshift using AWS SCT | Amazon Web Services
18 October 2023, AWS Blog

Azure Synapse Analytics: Everything you need to know about Microsoft's cloud analytics platform
24 September 2023, DataScientest

Azure Synapse vs. Databricks: Data Platform Comparison 2024
26 March 2024, eWeek

Azure Synapse Link for Cosmos DB: New Analytics Capabilities
10 November 2023, InfoQ.com

Azure Synapse Analytics vs Snowflake: ETL Tool Comparison
25 July 2023, TechRepublic

provided by Google News

Share this page