DBMS > Badger vs. EsgynDB vs. Riak KV vs. VoltDB

System Properties Comparison Badger vs. EsgynDB vs. Riak KV vs. VoltDB

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.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Distributed, fault tolerant key-value store

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Key-value store

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Relational DBMS

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

Score	0.20
Rank	#325	Overall
	#49	Key-value stores

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	4.44
Rank	#80	Overall
	#9	Key-value stores

Score	1.46
Rank	#159	Overall
	#74	Relational DBMS

Website

github.com/dgraph-io/badger

www.esgyn.cn

www.voltdb.com

Technical documentation

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

www.tiot.jp/riak-docs/riak/kv/latest

docs.voltdb.com

Developer

DGraph Labs

Esgyn

OpenSource, formerly Basho Technologies

VoltDB Inc.

Initial release

2017

2015

2009

2010

Current release

3.2.0, December 2022

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache version 2, commercial enterprise edition

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

C++, Java

Erlang

Java, C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux

Linux
OS X

for development

Data scheme

schema-free

yes

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

restricted

yes

SQL

Support of SQL

yes

only a subset of SQL 99

APIs and other access methods

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

Java Stored Procedures

Erlang

Java

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication between multi datacenters

selectable replication factor

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

User concepts

Access control

fine grained access rights according to SQL-standard

yes, using Riak Security

Users and roles with access to stored procedures

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

Recent citations in the news

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

Basho Revamps Riak Open-Source Database
17 September 2014, InformationWeek

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

Riak Taps Mesos for 'Push Button' NoSQL Scalability
20 August 2015, Datanami

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Combines Streaming, Global Data
1 February 2017, Datanami

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

provided by Google News

Share this page