DBMS > GeoMesa vs. Google Cloud Datastore vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. SAP SQL Anywhere

System Properties Comparison GeoMesa vs. Google Cloud Datastore vs. Microsoft Azure Table Storage vs. Microsoft SQL Server vs. SAP SQL Anywhere

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

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

Microsofts flagship relational DBMS

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	4.48
Rank	#75	Overall
	#6	Wide column stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

www.geomesa.org

cloud.google.com/datastore

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

www.microsoft.com/en-us/sql-server

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

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

cloud.google.com/datastore/docs

learn.microsoft.com/en-US/sql/sql-server

help.sap.com/docs/SAP_SQL_Anywhere

Developer

CCRi and others

Google

Microsoft

SAP

formerly Sybase

Initial release

2014

2008

2012

1989

1992

Current release

4.0.5, February 2024

SQL Server 2022, November 2022

17, July 2015

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

restricted free version is available

commercial

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++

Server operating systems

hosted

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language (GQL)

yes

APIs and other access methods

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

RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

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

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

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

Server-side scripts

Stored procedures

using Google App Engine

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes, in C/C++, Java, .Net or Perl

Triggers

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Implicit feature of the cloud service

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication using Paxos

yes

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

yes, but depending on the SQL-Server Edition

Source-replica replication

Database mirroring

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

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

optimistic locking

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights based on private key authentication or shared access signatures

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.