DB-EnginesExtremeDB: mitigate connectivity issues in a DBMSEnglish
Deutsch
Knowledge Base of Relational and NoSQL Database Management Systemsprovided by solid IT

DBMS > GeoMesa vs. Linter vs. RavenDB vs. WakandaDB

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

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines
NameGeoMesa  Xexclude from comparisonLinter  Xexclude from comparisonRavenDB  Xexclude from comparisonWakandaDB  Xexclude from comparison
DescriptionGeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.RDBMS for high security requirementsOpen Source Operational and Transactional Enterprise NoSQL Document DatabaseWakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data
Primary database modelSpatial DBMSRelational DBMSDocument storeObject oriented DBMS
Secondary database modelsSpatial DBMSGraph DBMS
Spatial DBMS
Time Series DBMS
DB-Engines Ranking infomeasures the popularity of database management systemsranking trend
Trend Chart
Score0.86
Rank#205  Overall
#4  Spatial DBMS
Score0.12
Rank#350  Overall
#152  Relational DBMS
Score2.84
Rank#101  Overall
#18  Document stores
Score0.10
Rank#356  Overall
#16  Object oriented DBMS
Websitewww.geomesa.orglinter.ruravendb.netwakanda.github.io
Technical documentationwww.geomesa.org/­documentation/­stable/­user/­index.htmlravendb.net/­docswakanda.github.io/­doc
DeveloperCCRi and othersrelex.ruHibernating RhinosWakanda SAS
Initial release2014199020102012
Current release5.0.0, May 20245.4, July 20222.7.0 (AprilĀ 29, 2019), April 2019
License infoCommercial or Open SourceOpen Source infoApache License 2.0commercialOpen Source infoAGPL version 3, commercial license availableOpen Source infoAGPLv3, extended commercial license available
Cloud-based only infoOnly available as a cloud servicenononono
DBaaS offerings (sponsored links) infoDatabase as a Service

Providers of DBaaS offerings, please contact us to be listed.
Implementation languageScalaC and C++C#C++, JavaScript
Server operating systemsAIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows
Linux
macOS
Raspberry Pi
Windows
Linux
OS X
Windows
Data schemeyesyesschema-freeyes
Typing infopredefined data types such as float or dateyesyesnoyes
XML support infoSome form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.nonono
Secondary indexesyesyesyes
SQL infoSupport of SQLnoyesSQL-like query language (RQL)no
APIs and other access methodsADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)
.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 languagesC
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl
.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
JavaScript
Server-side scripts infoStored proceduresnoyes infoproprietary syntax with the possibility to convert from PL/SQLyesyes
Triggersnoyesyesyes
Partitioning methods infoMethods for storing different data on different nodesdepending on storage layernoneShardingnone
Replication methods infoMethods for redundantly storing data on multiple nodesdepending on storage layerSource-replica replicationMulti-source replicationnone
MapReduce infoOffers an API for user-defined Map/Reduce methodsyesnoyesno
Consistency concepts infoMethods to ensure consistency in a distributed systemdepending on storage layerImmediate ConsistencyDefault 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 infoReferential integritynoyesno
Transaction concepts infoSupport to ensure data integrity after non-atomic manipulations of datanoACIDACID, Cluster-wide transaction availableACID
Concurrency infoSupport for concurrent manipulation of datayesyesyesyes
Durability infoSupport for making data persistentyesyesyesyes
In-memory capabilities infoIs there an option to define some or all structures to be held in-memory only.depending on storage layerno
User concepts infoAccess controlyes infodepending on the DBMS used for storagefine grained access rights according to SQL-standardAuthorization levels configured per client per databaseyes

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
GeoMesaLinterRavenDBWakandaDB
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
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

How I Created a RavenDB Python Client
23 September 2016, Visual Studio Magazine

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

provided by Google News



Share this page

Featured Products

Milvus logo

Vector database designed for GenAI, fully equipped for enterprise implementation.
Try Managed Milvus for Free

Datastax Astra logo

Bring all your data to Generative AI applications with vector search enabled by the most scalable
vector database available.
Try for Free

Neo4j logo

See for yourself how a graph database can make your life easier.
Use Neo4j online for free.

Present your product here