DBMS > BoltDB vs. Firebase Realtime Database vs. RocksDB vs. Tibero vs. Vitess

System Properties Comparison BoltDB vs. Firebase Realtime Database vs. RocksDB vs. Tibero vs. Vitess

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.

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

A secure RDBMS, designed for easy portability from Oracle

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	14.29
Rank	#39	Overall
	#6	Document stores

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

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

github.com/boltdb/bolt

firebase.google.com/products/realtime-database

rocksdb.org

us.tmaxsoft.com/products/tibero

vitess.io

Technical documentation

firebase.google.com/docs/database

github.com/facebook/rocksdb/wiki

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

vitess.io/docs

Developer

Google

acquired by Google 2014

Facebook, Inc.

TmaxSoft

The Linux Foundation, PlanetScale

Initial release

2013

2012

2013

2003

2013

Current release

8.11.4, April 2024

6, April 2015

15.0.2, December 2022

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

BSD

commercial

Open Source

Apache Version 2.0, commercial licenses available

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

C++

C and Assembler

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

Linux

AIX
HP-UX
Linux
Solaris
Windows

Docker
Linux
macOS

Data scheme

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

C++ API
Java API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Java
JavaScript
Objective-C

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

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

limited functionality with using 'rules'

Persistent Stored Procedure (PSM)

yes

proprietary syntax

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

by range, hash, list or composite

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

yes

ACID

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

planned for next version

yes

User concepts

Access control

yes, based on authentication and database rules

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.