DBMS > Couchbase vs. IBM Cloudant vs. OrigoDB vs. PouchDB

System Properties Comparison Couchbase vs. IBM Cloudant vs. OrigoDB vs. PouchDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Database as a Service offering based on Apache CouchDB

A fully ACID in-memory object graph database

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Document store

Document store
Object oriented DBMS

Document store

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	16.59
Rank	#36	Overall
	#5	Document stores

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Website

www.couchbase.com

www.ibm.com/products/cloudant

origodb.com

pouchdb.com

Technical documentation

docs.couchbase.com

cloud.ibm.com/docs/Cloudant

origodb.com/docs

pouchdb.com/guides

Developer

Couchbase, Inc.

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Robert Friberg et al

Apache Software Foundation

Initial release

2011

2010

2009

under the name LiveDB

2012

Current release

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

7.1.1, June 2019

License

Commercial or Open Source

Open Source

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

commercial

Open Source

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C, C++, Go and Erlang

Erlang

JavaScript

Server operating systems

Linux
OS X
Windows

hosted

Linux
Windows

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

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

via views

SQL

Support of SQL

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

APIs and other access methods

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

RESTful HTTP/JSON API

.NET Client API
HTTP API
LINQ

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net

JavaScript

Server-side scripts

Stored procedures

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

View functions (Map-Reduce) in JavaScript

yes

View functions in JavaScript

Triggers

yes

via the TAP protocol

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication
Source-replica replication

Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

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

Eventual Consistency

Foreign keys

Referential integrity

depending on model

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

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

Access rights for users can be defined per database

Role based authorization

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.