DBMS > GeoMesa vs. Immudb vs. Kinetica vs. Snowflake vs. Spark SQL

System Properties Comparison GeoMesa vs. Immudb vs. Kinetica vs. Snowflake vs. Spark SQL

Editorial information provided by DB-Engines

Name

Description

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

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

Fully vectorized database across both GPUs and CPUs

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

Primary database model

Spatial DBMS

Key-value store

Relational DBMS

Secondary database models

Relational DBMS

Spatial DBMS
Time Series DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.31
Rank	#295	Overall
	#42	Key-value stores

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Website

www.geomesa.org

github.com/codenotary/immudb
immudb.io

www.kinetica.com

www.snowflake.com

spark.apache.org/sql

Technical documentation

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

docs.immudb.io

docs.kinetica.com

docs.snowflake.net/manuals/index.html

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

CCRi and others

Codenotary

Kinetica

Snowflake Computing Inc.

Apache Software Foundation

Initial release

2014

2020

2012

2014

Current release

5.0.0, May 2024

1.2.3, April 2022

7.1, August 2021

3.5.0 ( 2.13), September 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache Version 2.0

commercial

Open Source

Apache 2.0

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

Scala

Server operating systems

BSD
Linux
macOS
Solaris
Windows
z/OS

Linux

hosted

Linux
OS X
Windows

Data scheme

yes

schema-free

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

SQL-like syntax

SQL-like DML and DDL statements

yes

SQL-like DML and DDL statements

APIs and other access methods

gRPC protocol
PostgreSQL wire protocol

JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

JDBC
ODBC

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
Python

C++
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Java
Python
R
Scala

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

yes

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

yes

none

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

Immediate Consistency or Eventual Consistency depending on configuration

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

GPU vRAM or System RAM

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users and roles on table level

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.