DBMS > GeoMesa vs. Oracle vs. Prometheus vs. Riak KV

System Properties Comparison GeoMesa vs. Oracle vs. Prometheus vs. Riak KV

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.

Widely used RDBMS

Open-source Time Series DBMS and monitoring system

Distributed, fault tolerant key-value store

Primary database model

with links between data sets and object tags for the creation of secondary indexes

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Website

www.geomesa.org

www.oracle.com/database

prometheus.io

Technical documentation

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

docs.oracle.com/en/database

prometheus.io/docs

www.tiot.jp/riak-docs/riak/kv/latest

Developer

CCRi and others

Oracle

OpenSource, formerly Basho Technologies

Initial release

2014

1980

2015

2009

Current release

5.0.0, May 2024

23c, September 2023

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

restricted free version is available

Open Source

Apache 2.0

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux
Windows

Linux
OS X

Data scheme

yes

Schemaless in JSON and XML columns

yes

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

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

Import of XML data possible

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

Supported programming languages

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding, horizontal partitioning

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication
Source-replica replication

yes

by Federation

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

none

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

ACID

isolation level can be parameterized

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

yes, using Riak Security

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.