DBMS > Amazon Redshift vs. CouchDB vs. Google Cloud Datastore vs. PouchDB vs. WakandaDB

System Properties Comparison Amazon Redshift vs. CouchDB vs. Google Cloud Datastore vs. PouchDB vs. WakandaDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

JavaScript DBMS with an API inspired by CouchDB

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Relational DBMS

Document store

Object oriented DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	7.46
Rank	#51	Overall
	#7	Document stores

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	2.18
Rank	#114	Overall
	#21	Document stores

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

aws.amazon.com/redshift

couchdb.apache.org

cloud.google.com/datastore

pouchdb.com

wakanda.github.io

Technical documentation

docs.aws.amazon.com/redshift

docs.couchdb.org/en/stable

cloud.google.com/datastore/docs

pouchdb.com/guides

wakanda.github.io/doc

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

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

Google

Apache Software Foundation

Wakanda SAS

Initial release

2012

2005

2008

2012

Current release

3.3.3, December 2023

7.1.1, June 2019

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

Open Source

AGPLv3, extended commercial license available

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

JavaScript

C++, JavaScript

Server operating systems

hosted

Android
BSD
Linux
OS X
Solaris
Windows

hosted

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

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

restricted

yes

via views

yes

via views

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language (GQL)

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

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

HTTP REST

only for PouchDB Server
JavaScript API

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

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

JavaScript

Server-side scripts

Stored procedures

user defined functions

in Python

View functions in JavaScript

using Google App Engine

View functions in JavaScript

yes

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

with a proxy-based framework, named couchdb-lounge

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Multi-source replication using Paxos

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

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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.

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

atomic operations within a single document possible

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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

fine grained access rights according to SQL-standard

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)

yes

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.