DBMS > GeoMesa vs. Microsoft SQL Server vs. MySQL vs. SpatiaLite

System Properties Comparison GeoMesa vs. Microsoft SQL Server vs. MySQL vs. SpatiaLite

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.

Microsofts flagship relational DBMS

Widely used open source RDBMS

Spatial extension of SQLite

Primary database model

Spatial DBMS

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

Relational DBMS

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

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	1.72
Rank	#149	Overall
	#3	Spatial DBMS

Website

www.geomesa.org

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

www.mysql.com

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

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

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

dev.mysql.com/doc

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

CCRi and others

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Alessandro Furieri

Initial release

2014

1989

1995

2008

Current release

4.0.5, February 2024

SQL Server 2022, November 2022

8.3.0, January 2024

5.0.0, August 2020

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

restricted free version is available

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Scala

C++

C and C++

C++

Server operating systems

Linux
Windows

FreeBSD
Linux
OS X
Solaris
Windows

server-less

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

with proprietary extensions

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

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

yes

proprietary syntax

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

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes, but depending on the SQL-Server Edition

Multi-source replication
Source-replica replication

none

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

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

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.