DBMS > GeoMesa vs. Hazelcast vs. Snowflake vs. SWC-DB vs. UniData,UniVerse

System Properties Comparison GeoMesa vs. Hazelcast vs. Snowflake vs. SWC-DB vs. UniData,UniVerse

Editorial information provided by DB-Engines

Name

Description

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

A widely adopted in-memory data grid

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

A high performance, scalable Wide Column DBMS

MultiValue database and application server with SQL mapping layer and meta database capabilities

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Time Series DBMS

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

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	6.87
Rank	#55	Overall
	#6	Key-value stores

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	0.01
Rank	#387	Overall
	#13	Wide column stores

Score	3.47
Rank	#93	Overall
	#2	Multivalue DBMS

Website

www.geomesa.org

hazelcast.com

www.snowflake.com

github.com/kashirin-alex/swc-db
www.swcdb.org

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-unidata

Technical documentation

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

hazelcast.org/imdg/docs

docs.snowflake.net/manuals/index.html

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

Developer

CCRi and others

Hazelcast

Snowflake Computing Inc.

Alex Kashirin

Rocket Software

Initial release

2014

2008

2014

2020

1985

Current release

4.0.5, February 2024

5.3.6, November 2023

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

GPL V3

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

Java

C++

Server operating systems

All OS with a Java VM

hosted

Linux

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

yes

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

schema-free

Typing

predefined data types such as float or date

yes

optional

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-like query language

yes

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

CLI Client
JDBC
ODBC

Proprietary protocol
Thrift

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

JavaScript (Node.js)
Python

C++

.Net
Basic

U2 Basic
C
Java

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

user defined functions

yes

Triggers

yes

Events

similar concept for controling cloud resources

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Replicated Map

yes

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 or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

one or two-phase-commit; repeatable reads; read commited

ACID

configurable

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

Role-based access control

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

Access rights according to SQL-standard and operating system based

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.