DBMS > Badger vs. GeoMesa vs. MarkLogic vs. NSDb vs. WakandaDB

System Properties Comparison Badger vs. GeoMesa vs. MarkLogic vs. NSDb vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

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

Operational and transactional Enterprise NoSQL database

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

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

Primary database model

Key-value store

Spatial DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Time Series DBMS

Object oriented DBMS

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

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

github.com/dgraph-io/badger

Technical documentation

godoc.org/github.com/dgraph-io/badger

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

docs.marklogic.com

nsdb.io/Architecture

wakanda.github.io/doc

Developer

DGraph Labs

CCRi and others

MarkLogic Corp.

Wakanda SAS

Initial release

2017

2014

2001

2017

2012

Current release

4.0.5, February 2024

11.0, December 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache License 2.0

commercial

restricted free version is available

Open Source

Apache Version 2.0

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

Java, Scala

C++, JavaScript

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Linux
macOS

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

Schema can be enforced

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

all fields are automatically indexed

SQL

Support of SQL

yes

SQL92

SQL-like query language

APIs and other access methods

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

gRPC
HTTP REST
WebSocket

RESTful HTTP API

Supported programming languages

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Java
Scala

JavaScript

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

none

depending on storage layer

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

can act as a resource manager in an XA/JTA transaction

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

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, with Range Indexes

User concepts

Access control

yes

depending on the DBMS used for storage

Role-based access control at the document and subdocument levels

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

MarkLogic “The NoSQL Database”. In the MarkLogic Query Console, you can… | by Abhay Srivastava | Apr, 2024
23 April 2024, Medium

Database Platform to Simplify Complex Data | Progress Marklogic
7 February 2023, Progress Software

ABN AMRO Moves Progress-Powered Credit Store App to Azure Cloud; Achieves 40% Faster Data Processing, Lower ...
12 March 2024, GlobeNewswire

Seven Quick Steps to Setting Up MarkLogic Server in Kubernetes
1 February 2024, biplatform.nl

Progress's $355m move for MarkLogic sets the tone for 2023
4 January 2023, The Stack

provided by Google News

Share this page