DBMS > GeoMesa vs. JSqlDb vs. Riak KV vs. YDB

System Properties Comparison GeoMesa vs. JSqlDb vs. Riak KV vs. YDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

JSqlDB seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

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

JavaScript Query Language Database, stores JavaScript objects and primitives

Distributed, fault tolerant key-value store

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Spatial DBMS

Document store
Object oriented DBMS

Key-value store

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

Document store
Relational DBMS

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

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Score	0.34
Rank	#285	Overall
	#43	Document stores
	#130	Relational DBMS

Website

www.geomesa.org

jsqldb.org (offline)

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

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

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

ydb.tech/en/docs

Developer

CCRi and others

Konrad von Backstrom

OpenSource, formerly Basho Technologies

Yandex

Initial release

2014

2018

2009

2019

Current release

4.0.5, February 2024

0.8, December 2018

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache version 2, commercial enterprise edition

Open Source

Apache 2.0; 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

Erlang

Server operating systems

Linux
macOS
Windows

Linux
OS X

Linux

Data scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, 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.

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

SQL-like query language (YQL)

APIs and other access methods

HTTP API
Native Erlang Interface

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

JavaScript

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

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

functions in JavaScript

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

no "single point of failure"

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

selectable replication factor

Active-passive shard 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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

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

using RocksDB

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

yes, using Riak Security

Access rights defined for Yandex Cloud users

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

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

Basho Revamps Riak Open-Source Database
17 September 2014, InformationWeek

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

Riak Taps Mesos for 'Push Button' NoSQL Scalability
20 August 2015, Datanami

provided by Google News

Personal Data Protection Service Initiates Probe into Yandex.Go App’s Data Processing
10 August 2023, Civil Georgia

Data leak from Russian delivery app shows dining habits of the secret police
3 April 2022, The Verge

Yandex code leak: Why hack of ‘Russian Google’s’ ranking factors has spooked the SEO industry
1 February 2023, The Indian Express

Russian secret police data leaked by food delivery app including where they live and what they eat...
4 April 2022, The US Sun

provided by Google News

Share this page