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

System Properties Comparison GeoMesa vs. Kingbase 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.

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

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
Spatial DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.50
Rank	#257	Overall
	#119	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.kingbase.com.cn

prometheus.io

Technical documentation

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

prometheus.io/docs

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

Developer

CCRi and others

BeiJing KINGBASE Information technologies inc.

OpenSource, formerly Basho Technologies

Initial release

2014

1999

2015

2009

Current release

5.0.0, May 2024

V8.0, August 2021

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

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 Java

Erlang

Server operating systems

Linux
Windows

Linux
OS X

Data scheme

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

Standard with numerous extensions

APIs and other access methods

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

RESTful HTTP/JSON API

HTTP API
Native Erlang Interface

Supported programming languages

.Net
C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

.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

user defined functions

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

by Federation

selectable replication factor

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

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

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

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.

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

Made in China 2025 is back, with a new name and a focus on database companies – The China Project
19 December 2022, The China Project

Opening preparation - Alekhine defense, Saemisch variation
18 April 2016, Chess.com

Backup & Recovery Solutions from China
4 August 2022, Хабр

provided by Google News

VTEX scales to 150 million metrics using Amazon Managed Service for Prometheus | Amazon Web Services
10 March 2024, AWS Blog

Exadata Real-Time Insight - Quick Start
3 April 2024, blogs.oracle.com

OpenTelemetry vs. Prometheus: You can’t fix what you can’t see
29 March 2024, IBM

VictoriaMetrics Offers Prometheus Replacement for Time Series Monitoring
17 July 2023, The New Stack

Linux System Monitoring with Prometheus, Grafana, and collectd
1 February 2024, Linux Journal

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Basho to Bolster Riak with DB Plug-Ins
5 May 2014, Datanami

Basho Advances NoSQL Riak Enterprise 2.0 With Search, Advanced Data Types
15 September 2014, Data Center Knowledge

provided by Google News

Share this page