DBMS > GeoMesa vs. HBase vs. Kinetica vs. SAP IQ vs. Snowflake

System Properties Comparison GeoMesa vs. HBase vs. Kinetica vs. SAP IQ vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

Wide-column store based on Apache Hadoop and on concepts of BigTable

Fully vectorized database across both GPUs and CPUs

Columnar RDBMS optimized for Big Data analytics

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

Primary database model

column-oriented

Secondary database models

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	27.97
Rank	#26	Overall
	#2	Wide column stores

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	2.64
Rank	#108	Overall
	#52	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.geomesa.org

hbase.apache.org

www.kinetica.com

www.sap.com/products/technology-platform/sybase-iq-big-data-management.html

www.snowflake.com

Technical documentation

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

hbase.apache.org/book.html

docs.kinetica.com

help.sap.com/docs/SAP_IQ

docs.snowflake.net/manuals/index.html

Developer

CCRi and others

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Kinetica

SAP, formerly Sybase

Snowflake Computing Inc.

Initial release

2014

2008

2012

1994

2014

Current release

5.0.0, May 2024

2.3.4, January 2021

7.1, August 2021

16.1 SPS04, April 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache version 2

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

Server operating systems

Linux
Unix
Windows

using Cygwin

Linux

AIX
HP-UX
Linux
Solaris
Windows

hosted

Data scheme

yes

schema-free, schema definition possible

yes

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

Typing

predefined data types such as float or date

yes

options to bring your own types, AVRO

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 DML and DDL statements

yes

APIs and other access methods

Java API
RESTful HTTP API
Thrift

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

C++
Java
JavaScript (Node.js)
Python

C
C#
C++
Java
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Coprocessors in Java

user defined functions

yes

user defined functions

Triggers

yes

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

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

shared disk or shared nothing architectures with SAP IQ Multiplexer

yes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication
Source-replica replication

Source-replica replication

SAP/Sybase Replication Server

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency or Eventual 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

Single row ACID (across millions of columns)

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 Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

Access rights for users and roles on table level

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.