DBMS > BoltDB vs. HBase vs. JanusGraph vs. RocksDB vs. Vitess

System Properties Comparison BoltDB vs. HBase vs. JanusGraph vs. RocksDB vs. Vitess

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

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

A Graph DBMS optimized for distributed clusters

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

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	1.94
Rank	#129	Overall
	#12	Graph DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

github.com/boltdb/bolt

Technical documentation

hbase.apache.org/book.html

docs.janusgraph.org

github.com/facebook/rocksdb/wiki

vitess.io/docs

Developer

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Linux Foundation; originally developed as Titan by Aurelius

Facebook, Inc.

The Linux Foundation, PlanetScale

Initial release

2013

2008

2017

2013

Current release

2.3.4, January 2021

0.6.3, February 2023

8.11.4, April 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache version 2

Open Source

Apache 2.0

Open Source

BSD

Open Source

Apache Version 2.0, commercial licenses available

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

Linux

Docker
Linux
macOS

Data scheme

schema-free

schema-free, schema definition possible

yes

schema-free

yes

Typing

predefined data types such as float or date

options to bring your own types, AVRO

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

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

Java API
RESTful HTTP API
Thrift

Java API
TinkerPop Blueprints
TinkerPop Frames
TinkerPop Gremlin
TinkerPop Rexster

C++ API
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

Clojure
Java
Python

C
C++
Go
Java
Perl
Python
Ruby

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Coprocessors in Java

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

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

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Faunus, a graph analytics engine

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

not for MyISAM storage engine

Transaction concepts

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

yes

Single row ACID (across millions of columns)

ACID

yes

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

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

User authentification and security via Rexster Graph Server

Users with fine-grained authorization concept

no user groups or 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.