DBMS > GeoMesa vs. Kinetica vs. Oracle Rdb vs. Sequoiadb vs. Snowflake

System Properties Comparison GeoMesa vs. Kinetica vs. Oracle Rdb vs. Sequoiadb vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

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

Fully vectorized database across both GPUs and CPUs

NewSQL database with distributed OLTP and SQL

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

Primary database model

Spatial DBMS

Relational DBMS

Document store
Relational DBMS

Relational DBMS

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	0.66
Rank	#234	Overall
	#107	Relational DBMS

Score	1.14
Rank	#178	Overall
	#80	Relational DBMS

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.geomesa.org

www.kinetica.com

www.oracle.com/database/technologies/related/rdb.html

www.sequoiadb.com

www.snowflake.com

Technical documentation

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

docs.kinetica.com

www.oracle.com/database/technologies/related/rdb-doc.html

www.sequoiadb.com/en/index.php?m=Files&a=index

docs.snowflake.net/manuals/index.html

Developer

CCRi and others

Kinetica

Oracle, originally developed by Digital Equipment Corporation (DEC)

Sequoiadb Ltd.

Snowflake Computing Inc.

Initial release

2014

2012

1984

2013

2014

Current release

5.0.0, May 2024

7.1, August 2021

7.4.1.1, 2021

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Server: AGPL; Client: Apache V2

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

C++

Server operating systems

Linux

HP Open VMS

Linux

hosted

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

schema-free

yes

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

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

proprietary protocol using JSON

CLI Client
JDBC
ODBC

Supported programming languages

C++
Java
JavaScript (Node.js)
Python

.Net
C++
Java
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

JavaScript

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

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

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 or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

Document is locked during a transaction

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

simple password-based access control

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.