DBMS > GeoMesa vs. Microsoft Azure SQL Database vs. MySQL vs. NSDb vs. OrigoDB

System Properties Comparison GeoMesa vs. Microsoft Azure SQL Database vs. MySQL vs. NSDb vs. OrigoDB

Editorial information provided by DB-Engines

Name

Description

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

Database as a Service offering with high compatibility to Microsoft SQL Server

Widely used open source RDBMS

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

A fully ACID in-memory object graph database

Primary database model

Spatial DBMS

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Document store
Object oriented DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Website

www.geomesa.org

azure.microsoft.com/en-us/products/azure-sql/database

www.mysql.com

nsdb.io

origodb.com

Technical documentation

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

docs.microsoft.com/en-us/azure/azure-sql

dev.mysql.com/doc

nsdb.io/Architecture

origodb.com/docs

Developer

CCRi and others

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Robert Friberg et al

Initial release

2014

2010

1995

2017

2009

under the name LiveDB

Current release

5.0.0, May 2024

V12

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0

Open Source

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.

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

Java, Scala

Server operating systems

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS

Linux
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

gRPC
HTTP REST
WebSocket

.NET Client API
HTTP API
LINQ

Supported programming languages

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

Java
Scala

.Net

Server-side scripts

Stored procedures

Transact SQL

yes

proprietary syntax

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes, with always 3 replicas available

Multi-source replication
Source-replica replication

Source-replica 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

not for MyISAM storage engine

depending on model

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

Using Apache Lucene

yes

Write ahead log

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

Role based authorization

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.