DBMS > Badger vs. Brytlyt vs. Drizzle vs. Riak KV

System Properties Comparison Badger vs. Brytlyt vs. Drizzle vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Distributed, fault tolerant key-value store

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

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

Score	0.14
Rank	#328	Overall
	#48	Key-value stores

Score	0.27
Rank	#292	Overall
	#132	Relational DBMS

Score	3.84
Rank	#76	Overall
	#9	Key-value stores

Website

github.com/dgraph-io/badger

brytlyt.io

Technical documentation

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

docs.brytlyt.io

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

Developer

DGraph Labs

Brytlyt

Drizzle project, originally started by Brian Aker

OpenSource, formerly Basho Technologies

Initial release

2017

2016

2008

2009

Current release

5.0, August 2023

7.2.4, September 2012

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GNU GPL

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

C, C++ and CUDA

C++

Erlang

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

FreeBSD
Linux
OS X

Linux
OS X

Data scheme

schema-free

yes

schema-free

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.

yes

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

restricted

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

JDBC

HTTP API
Native Erlang Interface

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C
C++
Java
PHP

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

user defined functions

in PL/pgSQL

Erlang

Triggers

yes

hooks for callbacks inside the server can be used.

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

Source-replica replication

Multi-source replication
Source-replica replication

selectable replication factor

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

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.

User concepts

Access control

fine grained access rights according to SQL-standard

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Dgraph raises $11.5 million for scalable graph database solutions
31 July 2019, VentureBeat

provided by Google News

Opensignal Announces Acquisition of Brytlyt GPU-based Data Analytics & Visualization Technology
5 June 2024, PR Web

Brytlyt releases version 5.0, introducing a more intuitive, intelligent and flexible analytics platform
1 August 2023, PR Newswire

Bringing GPUs To Bear On Bog Standard Relational Databases
26 February 2018, The Next Platform

Brytlyt Unleashes Serverless GPU-Acceleration for Analytics
15 September 2021, PR Newswire

Dell Technologies Helps Professionals Stay Productive Anywhere
21 May 2020, AiThority

provided by Google News

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

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

Basho aims for enterprise operational simplicity with new Data Platform
26 May 2015, diginomica

Is Riak A Good NoSQL Database Option For Enterprises?
1 July 2019, AIM

provided by Google News

Share this page