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

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

Editorial information provided by DB-Engines

Name

Description

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

JavaScript DBMS with an API inspired by CouchDB

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

Open source search engine for searching in data from different sources, e.g. relational databases

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

Primary database model

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

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

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	0.07
Rank	#349	Overall
	#32	Time Series DBMS

Website

Technical documentation

bigchaindb.readthedocs.io/en/latest

pouchdb.com/guides

github.com/facebook/rocksdb/wiki

sphinxsearch.com/docs

www.warp10.io/content/02_Getting_started

Developer

Apache Software Foundation

Facebook, Inc.

Sphinx Technologies Inc.

SenX

Initial release

2016

2012

2013

2001

2015

Current release

7.1.1, June 2019

9.2.1, May 2024

3.5.1, February 2023

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

BSD

Open Source

GPL version 2, commercial licence available

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

JavaScript

C++

Java

Server operating systems

Linux

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

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Windows

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

yes

full-text index on all search fields

SQL

Support of SQL

SQL-like query language (SphinxQL)

APIs and other access methods

CLI Client
RESTful HTTP API

HTTP REST

only for PouchDB Server
JavaScript API

C++ API
Java API

Proprietary protocol

HTTP API
Jupyter
WebSocket

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

JavaScript

C
C++
Go
Java
Perl
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

View functions in JavaScript

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

none

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

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

The original contents of fields are not stored in the Sphinx index.

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

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.