DBMS > GeoMesa vs. RavenDB vs. Sphinx vs. WakandaDB

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Open source search engine for searching in data from different sources, e.g. relational databases

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

Primary database model

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	2.84
Rank	#101	Overall
	#18	Document stores

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.10
Rank	#356	Overall
	#16	Object oriented DBMS

Website

Technical documentation

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

ravendb.net/docs

sphinxsearch.com/docs

wakanda.github.io/doc

Developer

CCRi and others

Hibernating Rhinos

Sphinx Technologies Inc.

Wakanda SAS

Initial release

2014

2010

2001

2012

Current release

5.0.0, May 2024

5.4, July 2022

3.5.1, February 2023

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

GPL version 2, commercial licence 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

C++

C++, JavaScript

Server operating systems

Linux
macOS
Raspberry Pi
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
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.

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

SQL-like query language (RQL)

SQL-like query language (SphinxQL)

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

Proprietary protocol

RESTful HTTP API

Supported programming languages

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

JavaScript

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Multi-source replication

none

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

The original contents of fields are not stored in the Sphinx index.

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

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

The DB-Engines ranking includes now search engines
4 February 2013, Paul Andlinger

show all

Recent citations in the 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

Review: NoSQL database RavenDB
20 March 2019, TechGenix

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

provided by Google News

Switching From Sphinx to MkDocs Documentation — What Did I Gain and Lose
2 February 2024, Towards Data Science

Manticore is a Faster Alternative to Elasticsearch in C++
25 July 2022, hackernoon.com

Perplexity AI: From Its Use To Operation, Everything You Need To Know About Google's Newest Challenger
11 January 2024, Free Press Journal

The Pirate Bay was recently down for over a week due to a DDoS attack
29 October 2019, The Hacker News

How to Build 600+ Links in One Month
4 September 2020, Search Engine Journal

provided by Google News

Share this page