DBMS > GeoMesa vs. Hypertable vs. Microsoft Azure SQL Database vs. mSQL vs. Snowflake

System Properties Comparison GeoMesa vs. Hypertable vs. Microsoft Azure SQL Database vs. mSQL vs. Snowflake

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

Description

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

An open source BigTable implementation based on distributed file systems such as Hadoop

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Spatial DBMS

Wide column store

Relational DBMS

Secondary database models

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.geomesa.org

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

hughestech.com.au/products/msql

www.snowflake.com

Technical documentation

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

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

docs.snowflake.net/manuals/index.html

Developer

CCRi and others

Hypertable Inc.

Microsoft

Hughes Technologies

Snowflake Computing Inc.

Initial release

2014

2009

2010

1994

2014

Current release

4.0.5, February 2024

0.9.8.11, March 2016

V12

4.4, October 2021

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

GNU version 3. Commercial license available

commercial

free licenses can be provided

commercial

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

Server operating systems

Linux
OS X
Windows

an inofficial Windows port is available

hosted

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

hosted

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

restricted

only exact value or prefix value scans

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

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

yes

APIs and other access methods

C++ API
Thrift

ADO.NET
JDBC
ODBC

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

C++
Java
Perl
PHP
Python
Ruby

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

C
C++
Delphi
Java
Perl
PHP
Tcl

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Transact SQL

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

selectable replication factor on file system level

yes, with always 3 replicas available

none

yes

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

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

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, user roles and pluggable authentication

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.