DBMS > Badger vs. SwayDB vs. Transwarp KunDB

System Properties Comparison Badger vs. SwayDB vs. Transwarp KunDB

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.

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

OLTP DBMS based on a distributed architecture and highly compatible with MySQL and Oracle

Primary database model

Key-value store

Relational 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.04
Rank	#387	Overall
	#61	Key-value stores

Score	0.14
Rank	#341	Overall
	#149	Relational DBMS

Website

github.com/dgraph-io/badger

swaydb.simer.au

www.transwarp.cn/en/product/kundb

Technical documentation

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

Developer

DGraph Labs

Simer Plaha

Transwarp

Initial release

2017

2018

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GNU Affero GPL V3.0

commercial

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

Server operating systems

BSD
Linux
OS X
Solaris
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

Supported programming languages

Java
Kotlin
Scala

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of operations

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.

yes

User concepts

Access control

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