DBMS > GeoMesa vs. Kinetica vs. Postgres-XL vs. RavenDB

System Properties Comparison GeoMesa vs. Kinetica vs. Postgres-XL vs. RavenDB

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.

Fully vectorized database across both GPUs and CPUs

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Spatial DBMS

Relational DBMS

Document store

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Spatial DBMS

Graph 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.66
Rank	#234	Overall
	#107	Relational DBMS

Score	0.53
Rank	#254	Overall
	#117	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Website

Technical documentation

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

docs.kinetica.com

www.postgres-xl.org/documentation

ravendb.net/docs

Developer

CCRi and others

Kinetica

Hibernating Rhinos

Initial release

2014

2012

2014

since 2012, originally named StormDB

2010

Current release

5.0.0, May 2024

7.1, August 2021

10 R1, October 2018

5.4, July 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Mozilla public license

Open Source

AGPL version 3, commercial license available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

C, C++

Server operating systems

Linux

Linux
macOS

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

schema-free

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

distributed, parallel query execution

SQL-like query language (RQL)

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

C++
Java
JavaScript (Node.js)
Python

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

yes

Triggers

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

Multi-source 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 depending on configuration

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

MVCC

ACID, Cluster-wide transaction available

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

fine grained access rights according to SQL-standard

Authorization levels configured per client per database

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Kinetica Delivers Real-Time Vector Similarity Search
21 March 2024, insideBIGDATA

Kinetica Elevates RAG with Fast Access to Real-Time Data
26 March 2024, Datanami

Kinetica ramps up RAG for generative AI, empowering enterprises with real-time operational data
18 March 2024, SiliconANGLE News

Kinetica Launches Generative AI Solution for Real-Time Inferencing Powered by NVIDIA AI Enterprise
18 March 2024, GlobeNewswire

Transforming spatiotemporal data analysis with GPUs and generative AI
30 October 2023, InfoWorld

provided by Google News

RavenDB Launches Version 6.0 Lightning Fast Queries, Data Integrations, Corax Indexing Engine, and Sharding
3 October 2023, PR Newswire

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

RavenDB Adds Graph Queries
15 May 2019, Datanami

Review: NoSQL database RavenDB
20 March 2019, TechGenix

RavenDB Welcomes David Baruc as Chief Revenue Officer: Seasoned Tech Leader to Drive Global Sales and ...
13 June 2023, PR Newswire

provided by Google News

Share this page