DBMS > BigchainDB vs. CouchDB vs. PouchDB vs. RocksDB vs. Warp 10

System Properties Comparison BigchainDB vs. CouchDB vs. PouchDB vs. RocksDB vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

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

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

JavaScript DBMS with an API inspired by CouchDB

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

Document store

Key-value store

Time Series DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

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

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.couchdb.org/en/stable

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

www.warp10.io/content/02_Getting_started

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Apache Software Foundation

Facebook, Inc.

SenX

Initial release

2016

2005

2012

2013

2015

Current release

3.3.3, December 2023

7.1.1, June 2019

9.2.1, May 2024

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache version 2

Open Source

BSD

Open Source

Apache License 2.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

Python

Erlang

JavaScript

C++

Java

Server operating systems

Linux

Android
BSD
Linux
OS X
Solaris
Windows

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

Linux

Linux
OS X
Windows

Data scheme

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

yes

via views

SQL

Support of SQL

APIs and other access methods

CLI Client
RESTful HTTP API

RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

HTTP API
Jupyter
WebSocket

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

View functions in JavaScript

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication
Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

selectable replication factor

based on HBase

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

based on HBase

Foreign keys

Referential integrity

Transaction concepts

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

atomic operations within a single document possible

yes

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

User concepts

Access control

yes

Access rights for users can be defined per database

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.