DBMS > GeoMesa vs. Google Cloud Datastore vs. Microsoft SQL Server vs. SAP SQL Anywhere vs. Vertica

System Properties Comparison GeoMesa vs. Google Cloud Datastore vs. Microsoft SQL Server vs. SAP SQL Anywhere vs. Vertica

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

Microsofts flagship relational DBMS

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

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Spatial DBMS

Document store

Relational DBMS

Column oriented

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Spatial DBMS
Time Series 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	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	10.68
Rank	#43	Overall
	#27	Relational DBMS

Website

www.geomesa.org

cloud.google.com/datastore

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

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

www.vertica.com

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

vertica.com/documentation

Developer

CCRi and others

Google

Microsoft

SAP

formerly Sybase

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2014

2008

1989

1992

2005

Current release

4.0.5, February 2024

SQL Server 2022, November 2022

17, July 2015

12.0.3, January 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

restricted free version is available

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

yes

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

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

Linux

Data scheme

yes

schema-free

yes

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

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

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

SQL-like query language (GQL)

yes

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

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

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

ADO.NET
HTTP API
JDBC
ODBC

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Supported programming languages

.Net
Go
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

C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R

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

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

Callbacks using the Google Apps Engine

yes

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

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

none

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication using Paxos

yes, but depending on the SQL-Server Edition

Source-replica replication

Database mirroring

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Bi-directional Spark integration

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

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)

fine grained access rights according to SQL-standard

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

More information provided by the system vendor

Specific characteristics

Deploy-anywhere database for large-scale analytical deployments. Deploy off-cloud,...
» more

Competitive advantages

Fast, scalable, and capable of high concurrency. Separation of compute/storage leverages...
» more

Typical application scenarios

Communication and network analytics, Embedded analytics, Fraud monitoring and Risk...
» more

Key customers

Abiba Systems, Adform, adMarketplace, AmeriPride, Anritsu, AOL, Avito, Auckland Transport,...
» more

Licensing and pricing models

Cost-based models and subscription-based models are both available. One license is...
» more

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.