DBMS > GeoMesa vs. Google Cloud Spanner vs. KairosDB vs. Microsoft SQL Server

System Properties Comparison GeoMesa vs. Google Cloud Spanner vs. KairosDB vs. Microsoft SQL Server

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.

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

Distributed Time Series DBMS based on Cassandra or H2

Microsofts flagship relational DBMS

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.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	2.84
Rank	#100	Overall
	#51	Relational DBMS

Score	0.67
Rank	#233	Overall
	#20	Time Series DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Website

www.geomesa.org

cloud.google.com/spanner

github.com/kairosdb/kairosdb

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

Technical documentation

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

cloud.google.com/spanner/docs

kairosdb.github.io

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

Developer

CCRi and others

Google

Microsoft

Initial release

2014

2017

2013

1989

Current release

5.0.0, May 2024

1.2.2, November 2018

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache 2.0

commercial

restricted free version is available

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

Scala

Java

C++

Server operating systems

hosted

Linux
OS X
Windows

Linux
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

yes

Query statements complying to ANSI 2011

yes

APIs and other access methods

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

Graphite protocol
HTTP REST
Telnet API

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

Supported programming languages

Go
Java
JavaScript (Node.js)
Python

Java
JavaScript

Node.js
PHP
Python

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

Server-side scripts

Stored procedures

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

based on Cassandra

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

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication with 3 replicas for regional instances.

selectable replication factor

based on Cassandra

yes, but depending on the SQL-Server Edition

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

yes

Transaction concepts

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

ACID

Strict serializable isolation

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)

simple password-based access control

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.