DBMS > Badger vs. BigchainDB vs. FatDB vs. Heroic vs. RocksDB

System Properties Comparison Badger vs. BigchainDB vs. FatDB vs. Heroic vs. RocksDB

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Key-value store

Document store

Document store
Key-value store

Time Series DBMS

Key-value store

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

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	0.46
Rank	#265	Overall
	#22	Time Series DBMS

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

github.com/dgraph-io/badger

www.bigchaindb.com

github.com/spotify/heroic

rocksdb.org

Technical documentation

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

bigchaindb.readthedocs.io/en/latest

spotify.github.io/heroic

github.com/facebook/rocksdb/wiki

Developer

DGraph Labs

FatCloud

Spotify

Facebook, Inc.

Initial release

2017

2016

2012

2014

2013

Current release

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

AGPL v3

commercial

Open Source

Apache 2.0

Open Source

BSD

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

Python

Java

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux

Windows

Linux

Data scheme

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.

Secondary indexes

yes

via Elasticsearch

SQL

Support of SQL

Via inetgration in SQL Server

APIs and other access methods

CLI Client
RESTful HTTP API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

HQL (Heroic Query Language, a JSON-based language)
HTTP API

C++ API
Java API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

via applications

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

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

Can implement custom security layer via applications

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.