DBMS > BoltDB vs. Heroic vs. HugeGraph vs. RocksDB vs. Vitess

System Properties Comparison BoltDB vs. Heroic vs. HugeGraph vs. RocksDB vs. Vitess

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

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

A fast-speed and highly-scalable Graph DBMS

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	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.13
Rank	#336	Overall
	#32	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

github.com/spotify/heroic

github.com/hugegraph
hugegraph.apache.org

rocksdb.org

vitess.io

Technical documentation

spotify.github.io/heroic

hugegraph.apache.org/docs

github.com/facebook/rocksdb/wiki

vitess.io/docs

Developer

Spotify

Baidu

Facebook, Inc.

The Linux Foundation, PlanetScale

Initial release

2013

2014

2018

2013

Current release

0.9

8.11.4, April 2024

15.0.2, December 2022

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

Open Source

Apache Version 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
macOS
Unix

Linux

Docker
Linux
macOS

Data scheme

schema-free

yes

schema-free

yes

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

yes

also supports composite index and range index

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

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

Java API
RESTful HTTP API
TinkerPop Gremlin

C++ API
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Groovy
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

asynchronous Gremlin script jobs

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

depending on used storage backend, e.g. Cassandra and HBase

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

depending on used storage backend, e.g. Cassandra and HBase

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

via hugegraph-spark

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

edges in graph

yes

not for MyISAM storage engine

Transaction concepts

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

yes

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

In-memory capabilities

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

yes

User concepts

Access control

Users, roles and permissions

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.