DBMS > Badger vs. JanusGraph vs. Oracle NoSQL vs. RocksDB

System Properties Comparison Badger vs. JanusGraph vs. Oracle NoSQL 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.

A Graph DBMS optimized for distributed clusters

It was forked from the latest code base of Titan in January 2017

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

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

Primary database model

Key-value store

Graph DBMS

Document store
Key-value store
Relational 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	2.02
Rank	#125	Overall
	#12	Graph DBMS

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

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

Website

github.com/dgraph-io/badger

janusgraph.org

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

rocksdb.org

Technical documentation

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

docs.janusgraph.org

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

github.com/facebook/rocksdb/wiki

Developer

DGraph Labs

Linux Foundation; originally developed as Titan by Aurelius

Oracle

Facebook, Inc.

Initial release

2017

2011

2013

Current release

0.6.3, February 2023

24.1, May 2024

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

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

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
OS X
Unix
Windows

Linux
Solaris SPARC/x86

Linux

Data scheme

schema-free

yes

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

yes

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

SQL

Support of SQL

SQL-like DML and DDL statements

APIs and other access methods

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

RESTful HTTP API

C++ API
Java API

Supported programming languages

Clojure
Java
Python

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

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

depending on the used storage backend (e.g. Cassandra, HBase, BerkeleyDB)

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

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

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

depending on configuration

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Supports various storage backends: Cassandra, HBase, Berkeley DB, Akiban, Hazelcast

yes

In-memory capabilities

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

yes

off heap cache

yes

User concepts

Access control

User authentification and security via Rexster Graph Server

Access rights for users and roles

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.