DBMS > BoltDB vs. Firebase Realtime Database vs. Hive vs. RocksDB vs. VoltDB

System Properties Comparison BoltDB vs. Firebase Realtime Database vs. Hive vs. RocksDB vs. VoltDB

Editorial information provided by DB-Engines

Name

Description

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

data warehouse software for querying and managing large distributed datasets, built on Hadoop

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

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

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

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	61.17
Rank	#18	Overall
	#12	Relational DBMS

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

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

github.com/boltdb/bolt

firebase.google.com/products/realtime-database

hive.apache.org

rocksdb.org

www.voltdb.com

Technical documentation

firebase.google.com/docs/database

cwiki.apache.org/confluence/display/Hive/Home

github.com/facebook/rocksdb/wiki

docs.voltdb.com

Developer

Google

acquired by Google 2014

Apache Software Foundation

initially developed by Facebook

Facebook, Inc.

VoltDB Inc.

Initial release

2013

2012

2013

2010

Current release

3.1.3, April 2022

8.11.4, April 2024

11.3, April 2022

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

Apache Version 2

Open Source

BSD

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Java, C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

All OS with a Java VM

Linux

Linux
OS X

for development

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

SQL

Support of SQL

SQL-like DML and DDL statements

yes

only a subset of SQL 99

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC
Thrift

C++ API
Java API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

Java
JavaScript
Objective-C

C++
Java
PHP
Python

C
C++
Go
Java
Perl
Python
Ruby

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

user defined functions and integration of map-reduce

Java

Triggers

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Eventual Consistency

Foreign keys

Referential integrity

FOREIGN KEY constraints are not supported

Transaction concepts

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

yes

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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, based on authentication and database rules

Access rights for users, groups and roles

Users and roles with access to stored procedures

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.