DBMS > BoltDB vs. HBase vs. PouchDB vs. RocksDB vs. YottaDB

System Properties Comparison BoltDB vs. HBase vs. PouchDB vs. RocksDB vs. YottaDB

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

JavaScript DBMS with an API inspired by CouchDB

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

A fast and solid embedded Key-value store

Primary database model

Secondary database models

Relational DBMS

using the Octo plugin

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	2.28
Rank	#115	Overall
	#21	Document stores

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

Score	0.20
Rank	#317	Overall
	#47	Key-value stores

Website

github.com/boltdb/bolt

Technical documentation

hbase.apache.org/book.html

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

yottadb.com/resources/documentation

Developer

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Apache Software Foundation

Facebook, Inc.

YottaDB, LLC

Initial release

2013

2008

2012

2013

2001

Current release

2.3.4, January 2021

7.1.1, June 2019

9.2.1, May 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache version 2

Open Source

BSD

Open Source

AGPL 3.0

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

JavaScript

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux
Unix
Windows

using Cygwin

server-less, requires a JavaScript environment (browser, Node.js)

Linux

Docker
Linux

Data scheme

schema-free

schema-free, schema definition possible

schema-free

Typing

predefined data types such as float or date

options to bring your own types, AVRO

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 views

SQL

Support of SQL

by using the Octo plugin

APIs and other access methods

Java API
RESTful HTTP API
Thrift

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

Coprocessors in Java

View functions in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

Single row ACID (across millions of columns)

yes

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

Users and groups based on OS-security mechanisms

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.