DBMS > CouchDB vs. LevelDB vs. PouchDB vs. RisingWave vs. SQLite

System Properties Comparison CouchDB vs. LevelDB vs. PouchDB vs. RisingWave vs. SQLite

Editorial information provided by DB-Engines

Name

Description

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

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

JavaScript DBMS with an API inspired by CouchDB

A distributed RDBMS for stream processing, wire-compatible with PostgreSQL

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	0.64
Rank	#238	Overall
	#110	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

couchdb.apache.org

github.com/google/leveldb

pouchdb.com

www.risingwave.com/database

www.sqlite.org

Technical documentation

docs.couchdb.org/en/stable

github.com/google/leveldb/blob/main/doc/index.md

pouchdb.com/guides

docs.risingwave.com/docs/current/intro

www.sqlite.org/docs.html

Developer

Apache Software Foundation

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

Google

Apache Software Foundation

RisingWave Labs

Dwayne Richard Hipp

Initial release

2005

2011

2012

2022

2000

Current release

3.3.3, December 2023

1.23, February 2021

7.1.1, June 2019

1.2, September 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

BSD

Open Source

Apache Version 2.0

Open Source

Public Domain

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

Erlang

C++

JavaScript

Rust

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Illumos
Linux
OS X
Windows

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

Docker
Linux
macOS

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

Standard SQL-types and JSON

yes

not rigid because of 'dynamic typing' concept.

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

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

JDBC
PostgreSQL wire protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

JavaScript

Go
Java
JavaScript (Node.js)
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

View functions in JavaScript

UDFs in Python or Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

Sharding

with a proxy-based framework, named couchdb-lounge

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

none

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

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

via file-system locks

Durability

Support for making data persistent

yes

with automatic compression on writes

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 rights for users can be defined per database

Users and Roles

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.