DBMS > GeoMesa vs. Microsoft SQL Server vs. Spark SQL vs. Transbase vs. VictoriaMetrics

System Properties Comparison GeoMesa vs. Microsoft SQL Server vs. Spark SQL vs. Transbase vs. VictoriaMetrics

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

A resource-optimized, high-performance, universally applicable RDBMS

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Spatial DBMS

Relational DBMS

Time Series DBMS

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	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Score	1.23
Rank	#172	Overall
	#15	Time Series DBMS

Website

www.geomesa.org

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

spark.apache.org/sql

www.transaction.de/en/products/transbase.html

victoriametrics.com

Technical documentation

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

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

spark.apache.org/docs/latest/sql-programming-guide.html

www.transaction.de/en/products/transbase/features.html

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

CCRi and others

Microsoft

Apache Software Foundation

Transaction Software GmbH

VictoriaMetrics

Initial release

2014

1989

2014

1987

2018

Current release

5.0.0, May 2024

SQL Server 2022, November 2022

3.5.0 ( 2.13), September 2023

Transbase 8.3, 2022

v1.91, May 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

restricted free version is available

Open Source

Apache 2.0

commercial

free development license

Open Source

Apache Version 2.0

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

Scala

C and C++

Server operating systems

Linux
Windows

Linux
OS X
Windows

FreeBSD
Linux
macOS
Solaris
Windows

FreeBSD
Linux
macOS
OpenBSD

Data scheme

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

SQL-like DML and DDL statements

yes

APIs and other access methods

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

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

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

Java
Python
R
Scala

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

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

yes

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

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes, but depending on the SQL-Server Edition

none

Source-replica replication

Synchronous replication

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

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

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.