DBMS > Amazon DocumentDB vs. IBM Cloudant vs. PouchDB vs. Snowflake vs. SwayDB

System Properties Comparison Amazon DocumentDB vs. IBM Cloudant vs. PouchDB vs. Snowflake vs. SwayDB

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

Database as a Service offering based on Apache CouchDB

JavaScript DBMS with an API inspired by CouchDB

Cloud-based data warehousing service for structured and semi-structured data

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Document store

Relational DBMS

Key-value store

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

aws.amazon.com/documentdb

www.ibm.com/products/cloudant

pouchdb.com

www.snowflake.com

swaydb.simer.au

Technical documentation

aws.amazon.com/documentdb/resources

cloud.ibm.com/docs/Cloudant

pouchdb.com/guides

docs.snowflake.net/manuals/index.html

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Apache Software Foundation

Snowflake Computing Inc.

Simer Plaha

Initial release

2019

2010

2012

2014

2018

Current release

7.1.1, June 2019

License

Commercial or Open Source

commercial

Open Source

commercial

Open Source

GNU Affero GPL V3.0

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

Scala

Server operating systems

hosted

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

hosted

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

schema-free

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

via views

SQL

Support of SQL

yes

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

RESTful HTTP/JSON API

HTTP REST

only for PouchDB Server
JavaScript API

CLI Client
JDBC
ODBC

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

C#
Java
JavaScript
Objective-C
PHP
Ruby

JavaScript

JavaScript (Node.js)
Python

Java
Kotlin
Scala

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

View functions in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

with a proxy-based framework, named couchdb-lounge

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

Multi-source replication
Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

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

Atomic single-document operations

atomic operations within a document possible

ACID

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

yes

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

Access rights for users and roles

Access rights for users can be defined per database

Users with fine-grained authorization concept, user roles and pluggable authentication

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.