DBMS > Badger vs. GeoMesa vs. Linter vs. WakandaDB

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

Please select another system to include it in the comparison.

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.

RDBMS for high security requirements

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

Spatial 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	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

github.com/dgraph-io/badger

www.geomesa.org

linter.ru

wakanda.github.io

Technical documentation

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

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

wakanda.github.io/doc

Developer

DGraph Labs

CCRi and others

relex.ru

Wakanda SAS

Initial release

2017

2014

1990

2012

Current release

5.0.0, May 2024

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

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

C++, JavaScript

Server operating systems

BSD
Linux
OS X
Solaris
Windows

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux
OS X
Windows

Data scheme

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

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

RESTful HTTP API

Supported programming languages

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

JavaScript

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

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

fine grained access rights according to SQL-standard

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.