DBMS > GeoMesa vs. GridGain vs. RavenDB vs. WakandaDB

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

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.

GridGain is an in-memory computing platform, built on Apache Ignite

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

Primary database model

Spatial DBMS

Key-value store
Relational DBMS

Document store

Object oriented 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.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	2.84
Rank	#101	Overall
	#18	Document stores

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

Technical documentation

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

www.gridgain.com/docs/index.html

ravendb.net/docs

wakanda.github.io/doc

Developer

CCRi and others

GridGain Systems, Inc.

Hibernating Rhinos

Wakanda SAS

Initial release

2014

2007

2010

2012

Current release

5.0.0, May 2024

GridGain 8.5.1

5.4, July 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

AGPL version 3, commercial license available

Open Source

AGPLv3, extended 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

Java, C++, .Net

C++, JavaScript

Server operating systems

Linux
OS X
Solaris
Windows

Linux
macOS
Raspberry Pi
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

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

Secondary indexes

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

SQL-like query language (RQL)

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

.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

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

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

JavaScript

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes (replicated cache)

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

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.

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

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

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Security Hooks for custom implementations

Authorization levels configured per client per database

yes

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

GridGain in-memory data and generative AI – Blocks and Files
10 May 2024, Blocks and Files

GridGain's 2023 Growth Positions Company for Strong 2024
24 January 2024, PR Newswire

GridGain Unified Real-Time Data Platform Version 8.9 Addresses Today's More Complex Real-Time Data Processing ...
12 October 2023, GlobeNewswire

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

GridGain — Extreme Speed and Scale for Data-Intensive Apps
21 September 2014, gridgain.com

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

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

Review: NoSQL database RavenDB
20 March 2019, TechGenix

provided by Google News

Share this page