DBMS > GeoMesa vs. mSQL vs. Postgres-XL vs. Splice Machine vs. SwayDB

System Properties Comparison GeoMesa vs. mSQL vs. Postgres-XL vs. Splice Machine vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Spatial DBMS

Relational DBMS

Key-value store

Secondary database models

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	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

www.geomesa.org

hughestech.com.au/products/msql

www.postgres-xl.org

splicemachine.com

swaydb.simer.au

Technical documentation

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

www.postgres-xl.org/documentation

splicemachine.com/how-it-works

Developer

CCRi and others

Hughes Technologies

Splice Machine

Simer Plaha

Initial release

2014

1994

2014

since 2012, originally named StormDB

2014

2018

Current release

5.0.0, May 2024

4.4, October 2021

10 R1, October 2018

3.1, March 2021

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free licenses can be provided

Open Source

Mozilla public license

Open Source

AGPL 3.0, commercial license available

Open Source

GNU Affero GPL V3.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.

Implementation language

Scala

Java

Scala

Server operating systems

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

Linux
macOS

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

A subset of ANSI SQL is implemented

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

yes

distributed, parallel query execution

yes

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

JDBC
Native Spark Datasource
ODBC

Supported programming languages

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Java
Kotlin
Scala

Server-side scripts

Stored procedures

user defined functions

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

horizontal partitioning

Shared Nothhing Auto-Sharding, Columnar Partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

MVCC

ACID

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

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

Access rights for users, groups and roles 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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Higher Education PS rules out ghost students before PAC
29 November 2018, diggers.news

provided by Google News

Machine learning data pipeline outfit Splice Machine files for insolvency
26 August 2021, The Register

Splice Machine Launches the Splice Machine Feature Store to Simplify Feature Engineering and Democratize Machine ...
19 January 2021, PR Newswire

Splice Machine Launches Feature Store to Simplify Feature Engineering
19 January 2021, Datanami

How Splice Machine's Data Platform for Intelligent Apps Works
29 September 2020, eWeek

New Splice Machine RDBMS unites OLTP and OLAP
18 November 2015, CIO

provided by Google News

Share this page