DBMS > Badger vs. Oracle NoSQL vs. Riak KV

System Properties Comparison Badger vs. Oracle NoSQL vs. Riak KV

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.

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Distributed, fault tolerant key-value store

Primary database model

Key-value store

Document store
Key-value store
Relational DBMS

Key-value store

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

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

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

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

github.com/dgraph-io/badger

www.oracle.com/database/nosql/technologies/nosql

Technical documentation

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

docs.oracle.com/en/database/other-databases/nosql-database/index.html

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

Developer

DGraph Labs

Oracle

OpenSource, formerly Basho Technologies

Initial release

2017

2011

2009

Current release

23.3, December 2023

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
Solaris SPARC/x86

Linux
OS X

Data scheme

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

schema-free

Typing

predefined data types such as float or date

optional

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

SQL

Support of SQL

SQL-like DML and DDL statements

APIs and other access methods

RESTful HTTP API

HTTP API
Native Erlang Interface

Supported programming languages

C
C#
Go
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

Erlang

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"

Replication methods

Methods for redundantly storing data on multiple nodes

none

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

depending on configuration

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

Transaction concepts

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

configurable

ACID within a storage node (=shard)

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

off heap cache

User concepts

Access control

Access rights for users and roles

yes, using Riak Security

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

Enhance enterprise data security and trust: Must see Blockchain Technology sessions at Oracle CloudWorld 2023
21 August 2023, Oracle

We built a geo-distributed, serverless modern app using the Oracle NoSQL Database Cloud Service
18 November 2021, Oracle

Oracle Beefs Up Its NoSQL Database Offering
3 April 2014, Data Center Knowledge

Oracle Defends Relational DBs Against NoSQL Competitors
25 November 2015, eWeek

NoSQL Rebels Aim Missile at Larry Ellison's Yacht
20 July 2012, WIRED

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

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

A Critique of Resizable Hash Tables: Riak Core & Random Slicing
26 August 2018, InfoQ.com

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

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

Share this page