DBMS > Badger vs. HBase vs. OrigoDB vs. RocksDB

System Properties Comparison Badger vs. HBase vs. OrigoDB vs. RocksDB

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.

Wide-column store based on Apache Hadoop and on concepts of BigTable

A fully ACID in-memory object graph database

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

Primary database model

Key-value store

Wide column store

Document store
Object oriented DBMS

Key-value store

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

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

Score	31.25
Rank	#26	Overall
	#2	Wide column stores

Score	0.03
Rank	#378	Overall
	#51	Document stores
	#18	Object oriented DBMS

Score	4.00
Rank	#84	Overall
	#11	Key-value stores

Website

github.com/dgraph-io/badger

hbase.apache.org

origodb.com

rocksdb.org

Technical documentation

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

hbase.apache.org/book.html

origodb.com/docs

github.com/facebook/rocksdb/wiki

Developer

DGraph Labs

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Robert Friberg et al

Facebook, Inc.

Initial release

2017

2008

2009

under the name LiveDB

2013

Current release

2.3.4, January 2021

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache version 2

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

Java

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
Unix
Windows

using Cygwin

Linux
Windows

Linux

Data scheme

schema-free

schema-free, schema definition possible

yes

schema-free

Typing

predefined data types such as float or date

options to bring your own types, AVRO

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

APIs and other access methods

Java API
RESTful HTTP API
Thrift

.NET Client API
HTTP API
LINQ

C++ API
Java API

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

.Net

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Coprocessors in Java

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

Single row ACID (across millions of columns)

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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

Access Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

Role based authorization

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.