DBMS > GeoMesa vs. mSQL vs. Snowflake vs. VelocityDB

System Properties Comparison GeoMesa vs. mSQL vs. Snowflake vs. VelocityDB

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.

mSQL (Mini SQL) is a simple and lightweight RDBMS

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

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Spatial DBMS

Relational DBMS

Graph DBMS
Object oriented 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	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.05
Rank	#358	Overall
	#36	Graph DBMS
	#16	Object oriented DBMS

Website

www.geomesa.org

hughestech.com.au/products/msql

www.snowflake.com

velocitydb.com

Technical documentation

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

docs.snowflake.net/manuals/index.html

velocitydb.com/UserGuide

Developer

CCRi and others

Hughes Technologies

Snowflake Computing Inc.

VelocityDB Inc

Initial release

2014

1994

2014

2011

Current release

4.0.5, February 2024

4.4, October 2021

7.x

License

Commercial or Open Source

Open Source

Apache License 2.0

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

Server operating systems

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

hosted

Any that supports .NET

Data scheme

yes

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

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

A subset of ANSI SQL is implemented

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

yes

APIs and other access methods

JDBC
ODBC

CLI Client
JDBC
ODBC

.Net

Supported programming languages

C
C++
Delphi
Java
Perl
PHP
Tcl

JavaScript (Node.js)
Python

.Net

Server-side scripts

Stored procedures

user defined functions

Triggers

similar concept for controling cloud resources

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

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

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

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Users with fine-grained authorization concept, user roles and pluggable authentication

Based on Windows 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.