DBMS > GeoMesa vs. Microsoft SQL Server vs. NSDb vs. SAP SQL Anywhere vs. XTDB

System Properties Comparison GeoMesa vs. Microsoft SQL Server vs. NSDb vs. SAP SQL Anywhere vs. XTDB

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Microsofts flagship relational DBMS

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

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

A general purpose database with bitemporal SQL and Datalog and graph queries

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	#214	Overall
	#4	Spatial DBMS

Score	807.76
Rank	#3	Overall
	#3	Relational DBMS

Score	0.00
Rank	#385	Overall
	#40	Time Series DBMS

Score	3.50
Rank	#81	Overall
	#44	Relational DBMS

Score	0.13
Rank	#330	Overall
	#45	Document stores

Website

www.geomesa.org

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

nsdb.io

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

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

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

nsdb.io/Architecture

help.sap.com/docs/SAP_SQL_Anywhere

www.xtdb.com/docs

Developer

CCRi and others

Microsoft

SAP

formerly Sybase

Juxt Ltd.

Initial release

2014

1989

2017

1992

2019

Current release

5.0.1, July 2024

SQL Server 2022, November 2022

17, July 2015

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

restricted free version is available

Open Source

Apache Version 2.0

commercial

Open Source

MIT License

Cloud-based only

Only available as a cloud service

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

C++

Java, Scala

Clojure

Server operating systems

Linux
Windows

Linux
macOS

AIX
HP-UX
Linux
OS X
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

yes

yes, extensible-data-notation format

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

all fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL-like query language

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

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

gRPC
HTTP REST
WebSocket

ADO.NET
HTTP API
JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

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

Java
Scala

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

Clojure
Java

Server-side scripts

Stored procedures

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

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes, but depending on the SQL-Server Edition

Source-replica replication

Database mirroring

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

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.