DBMS > GeoMesa vs. Microsoft Azure Cosmos DB vs. mSQL vs. SpatiaLite vs. XTDB

System Properties Comparison GeoMesa vs. Microsoft Azure Cosmos DB vs. mSQL vs. SpatiaLite vs. XTDB

Editorial information provided by DB-Engines

Name

Description

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

Globally distributed, horizontally scalable, multi-model database service

mSQL (Mini SQL) is a simple and lightweight RDBMS

Spatial extension of SQLite

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

Primary database model

Spatial DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Spatial DBMS

Document store

Secondary database models

Spatial DBMS

Relational DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.geomesa.org

azure.microsoft.com/services/cosmos-db

hughestech.com.au/products/msql

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

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

Technical documentation

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

learn.microsoft.com/azure/cosmos-db

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

www.xtdb.com/docs

Developer

CCRi and others

Microsoft

Hughes Technologies

Alessandro Furieri

Juxt Ltd.

Initial release

2014

1994

2008

2019

Current release

4.0.5, February 2024

4.4, October 2021

5.0.0, August 2020

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free licenses can be provided

Open Source

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

Open Source

MIT License

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.

Implementation language

Scala

C++

Clojure

Server operating systems

hosted

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

server-less

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

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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.

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

JDBC
ODBC

HTTP REST
JDBC

Supported programming languages

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

C
C++
Delphi
Java
Perl
PHP
Tcl

Clojure
Java

Server-side scripts

Stored procedures

JavaScript

Triggers

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Implicit feature of the cloud service

none

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

Access rights can be defined down to the item level

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.