DBMS > CouchDB vs. Google Cloud Datastore vs. Oracle vs. OrigoDB vs. PouchDB

System Properties Comparison CouchDB vs. Google Cloud Datastore vs. Oracle vs. OrigoDB vs. PouchDB

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.

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Widely used RDBMS

A fully ACID in-memory object graph database

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Document store

Relational DBMS

Document store
Object oriented DBMS

Document store

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	7.46
Rank	#51	Overall
	#7	Document stores

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	1286.59
Rank	#1	Overall
	#1	Relational DBMS

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Score	2.18
Rank	#114	Overall
	#21	Document stores

Website

couchdb.apache.org

cloud.google.com/datastore

www.oracle.com/database

origodb.com

pouchdb.com

Technical documentation

docs.couchdb.org/en/stable

cloud.google.com/datastore/docs

docs.oracle.com/en/database

origodb.com/docs

pouchdb.com/guides

Developer

Apache Software Foundation

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

Google

Oracle

Robert Friberg et al

Apache Software Foundation

Initial release

2005

2008

1980

2009

under the name LiveDB

2012

Current release

3.3.3, December 2023

23c, September 2023

7.1.1, June 2019

License

Commercial or Open Source

Open Source

Apache version 2

commercial

restricted free version is available

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

Erlang

C and C++

JavaScript

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Linux
Windows

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

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

yes

schema-free

Typing

predefined data types such as float or date

yes, details here

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.

yes

can be achieved using .NET

Secondary indexes

yes

via views

yes

via views

SQL

Support of SQL

SQL-like query language (GQL)

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP/JSON API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

.NET Client API
HTTP API
LINQ

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

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

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.Net

JavaScript

Server-side scripts

Stored procedures

View functions in JavaScript

using Google App Engine

PL/SQL

also stored procedures in Java possible

yes

View functions in JavaScript

Triggers

yes

Callbacks using the Google Apps Engine

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

Sharding, horizontal partitioning

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
Source-replica replication

Multi-source replication using Paxos

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

using Google Cloud Dataflow

can be realized in PL/SQL

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

depending on model

Transaction concepts

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

atomic operations within a single document possible

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: 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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

Access rights for users can be defined per database

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

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.