DBMS > BigchainDB vs. Couchbase vs. MaxDB vs. PouchDB vs. RocksDB

System Properties Comparison BigchainDB vs. Couchbase vs. MaxDB vs. PouchDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

A robust and reliable RDBMS optimized to run all major SAP solutions

JavaScript DBMS with an API inspired by CouchDB

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

Primary database model

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

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

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	2.26
Rank	#114	Overall
	#55	Relational DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.couchbase.com

maxdb.sap.com/documentation

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

Developer

Couchbase, Inc.

SAP, acquired from Software AG (Adabas-D) in 1997

Apache Software Foundation

Facebook, Inc.

Initial release

2016

2011

1984

2012

2013

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

7.9.10.12, February 2024

7.1.1, June 2019

9.2.1, May 2024

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

commercial

Limited community edition free

Open Source

BSD

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

Python

C, C++, Go and Erlang

C++

JavaScript

C++

Server operating systems

Linux

Linux
OS X
Windows

AIX
HP-UX
Linux
Solaris
Windows

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

Linux

Data scheme

schema-free

yes

schema-free

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 views

SQL

Support of SQL

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

yes

APIs and other access methods

CLI Client
RESTful HTTP API

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

ADO.NET
JDBC
ODBC
WebDAV

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

.Net
C#
Java
Perl
PHP
Python

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

yes

View functions in JavaScript

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic Sharding

none

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

including cross data center replication
Source-replica 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

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

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

Ephemeral buckets

yes

User concepts

Access control

yes

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

fine grained access rights according to SQL-standard

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.