DBMS > PouchDB vs. RavenDB vs. RocksDB vs. SWC-DB vs. TerarkDB

System Properties Comparison PouchDB vs. RavenDB vs. RocksDB vs. SWC-DB vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS with an API inspired by CouchDB

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

A high performance, scalable Wide Column DBMS

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

Time Series DBMS

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

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	2.92
Rank	#101	Overall
	#18	Document stores

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

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

pouchdb.com

ravendb.net

rocksdb.org

github.com/kashirin-alex/swc-db
www.swcdb.org

github.com/bytedance/terarkdb

Technical documentation

pouchdb.com/guides

ravendb.net/docs

github.com/facebook/rocksdb/wiki

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Apache Software Foundation

Hibernating Rhinos

Facebook, Inc.

Alex Kashirin

ByteDance, originally Terark

Initial release

2012

2010

2013

2020

2016

Current release

7.1.1, June 2019

5.4, July 2022

8.11.4, April 2024

0.5, April 2021

License

Commercial or Open Source

Open Source

AGPL version 3, commercial license available

Open Source

BSD

Open Source

GPL V3

commercial

restricted open source version available

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

JavaScript

C++

Server operating systems

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

Linux
macOS
Raspberry Pi
Windows

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

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

SQL

Support of SQL

SQL-like query language (RQL)

SQL-like query language

APIs and other access methods

HTTP REST

only for PouchDB Server
JavaScript API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

C++ API
Java API

Proprietary protocol
Thrift

C++ API
Java API

Supported programming languages

JavaScript

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

C++

C++
Java

Server-side scripts

Stored procedures

View functions in JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

with a proxy-based framework, named couchdb-lounge

Sharding

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Multi-source replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID, Cluster-wide transaction available

yes

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

Authorization levels configured per client per database

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.