DBMS > IBM Db2 vs. Memcached vs. Microsoft Azure Cosmos DB vs. PouchDB

System Properties Comparison IBM Db2 vs. Memcached vs. Microsoft Azure Cosmos DB vs. PouchDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Common in IBM host environments, 2 different versions for host and Windows/Linux

In-memory key-value store, originally intended for caching

Globally distributed, horizontally scalable, multi-model database service

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Key-value store

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

Spatial DBMS

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

Score	128.46
Rank	#8	Overall
	#5	Relational DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	2.28
Rank	#115	Overall
	#21	Document stores

Website

www.ibm.com/products/db2

www.memcached.org

azure.microsoft.com/services/cosmos-db

pouchdb.com

Technical documentation

www.ibm.com/docs/en/db2

github.com/memcached/memcached/wiki

learn.microsoft.com/azure/cosmos-db

pouchdb.com/guides

Developer

IBM

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Apache Software Foundation

Initial release

1983

host version

2003

2014

2012

Current release

12.1, October 2016

1.6.25, March 2024

7.1.1, June 2019

License

Commercial or Open Source

commercial

free version is available

Open Source

BSD license

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 and C++

JavaScript

Server operating systems

AIX
HP-UX
Linux
Solaris
Windows
z/OS

FreeBSD
Linux
OS X
Unix
Windows

hosted

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

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

via views

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

Proprietary protocol

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

JavaScript

Server-side scripts

Stored procedures

yes

JavaScript

View functions in JavaScript

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

only with Windows/Unix/Linux Version

none

Sharding

Implicit feature of the cloud service

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

yes

with separate tools (MQ, InfoSphere)

none

Repcached, a Memcached patch, provides this functionallity

yes

Implicit feature of the cloud service

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

User concepts

Access control

fine grained access rights according to SQL-standard

yes

using SASL (Simple Authentication and Security Layer) protocol

Access rights can be defined down to the item level

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.