DBMS > Badger vs. NSDb vs. OrigoDB vs. WakandaDB

System Properties Comparison Badger vs. NSDb vs. OrigoDB 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.

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

A fully ACID in-memory object graph database

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

Time Series DBMS

Document store
Object oriented DBMS

Object oriented DBMS

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

Score	0.22
Rank	#320	Overall
	#47	Key-value stores

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#19	Object oriented DBMS

Score	0.10
Rank	#356	Overall
	#17	Object oriented DBMS

Website

github.com/dgraph-io/badger

nsdb.io

origodb.com

wakanda.github.io

Technical documentation

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

nsdb.io/Architecture

origodb.com/docs

wakanda.github.io/doc

Developer

DGraph Labs

Robert Friberg et al

Wakanda SAS

Initial release

2017

2009

under the name LiveDB

2012

Current release

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache 2.0

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

Java, Scala

C++, JavaScript

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
macOS

Linux
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes: int, bigint, decimal, string

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

gRPC
HTTP REST
WebSocket

.NET Client API
HTTP API
LINQ

RESTful HTTP API

Supported programming languages

Java
Scala

.Net

JavaScript

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

Using Apache Lucene

yes

Write ahead log

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Role based authorization

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.

Share this page