DBMS > GeoMesa vs. RavenDB vs. WakandaDB vs. YDB

System Properties Comparison GeoMesa vs. RavenDB vs. WakandaDB vs. YDB

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.

Open Source Operational and Transactional Enterprise NoSQL Document Database

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

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

Document store
Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Score	0.35
Rank	#278	Overall
	#43	Document stores
	#127	Relational DBMS

Website

www.geomesa.org

ravendb.net

wakanda.github.io

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

Technical documentation

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

ravendb.net/docs

wakanda.github.io/doc

ydb.tech/en/docs

Developer

CCRi and others

Hibernating Rhinos

Wakanda SAS

Yandex

Initial release

2014

2010

2012

2019

Current release

4.0.5, February 2024

5.4, July 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

AGPL version 3, commercial license available

Open Source

AGPLv3, extended commercial license available

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

C++, JavaScript

Server operating systems

Linux
macOS
Raspberry Pi
Windows

Linux
OS X
Windows

Linux

Data scheme

yes

schema-free

yes

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

SQL

Support of SQL

SQL-like query language (RQL)

SQL-like query language (YQL)

APIs and other access methods

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

RESTful HTTP API

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

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

JavaScript

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication

none

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

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.

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID, Cluster-wide transaction available

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

Authorization levels configured per client per database

yes

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

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

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

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

Oren Eini on RavenDB, Including Consistency Guarantees and C# as the Implementation Language
23 May 2022, InfoQ.com

RavenDB Adds Graph Queries
15 May 2019, 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

Russian Court Sues Yandex CEO For LGBT Propaganda Case
3 January 2024, VOI.ID

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