DBMS > CouchDB vs. Ignite vs. MarkLogic vs. Microsoft Azure Cosmos DB vs. PouchDB

System Properties Comparison CouchDB vs. Ignite vs. MarkLogic vs. Microsoft Azure Cosmos DB 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.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Operational and transactional Enterprise NoSQL database

Globally distributed, horizontally scalable, multi-model database service

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Document store

Key-value store
Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Document store
Graph DBMS
Key-value store
Wide column store

Document store

Secondary database models

Spatial DBMS

using the Geocouch extension

Spatial DBMS

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

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	5.18
Rank	#63	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#7	Search engines

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

Score	2.34
Rank	#112	Overall
	#21	Document stores

Website

couchdb.apache.org

ignite.apache.org

www.progress.com/marklogic

azure.microsoft.com/services/cosmos-db

pouchdb.com

Technical documentation

docs.couchdb.org/en/stable

apacheignite.readme.io/docs

www.progress.com/marklogic/documentation

learn.microsoft.com/azure/cosmos-db

pouchdb.com/guides

Developer

Apache Software Foundation

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

Apache Software Foundation

MarkLogic Corp.

Microsoft

Apache Software Foundation

Initial release

2005

2015

2001

2014

2012

Current release

3.3.3, December 2023

Apache Ignite 2.6

11.0, December 2022

7.1.1, June 2019

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Apache 2.0

commercial

restricted free version is 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

Erlang

C++, Java, .Net

C++

JavaScript

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Linux
OS X
Windows

hosted

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

Data scheme

schema-free

yes

schema-free

Schema can be enforced

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.

yes

Secondary indexes

yes

via views

yes

All properties auto-indexed by default

yes

via views

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

SQL92

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

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#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Java
JavaScript (Node.js)
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

View functions in JavaScript

yes (compute grid and cache interceptors can be used instead)

yes

via XQuery or JavaScript

JavaScript

View functions in JavaScript

Triggers

yes

yes (cache interceptors and events)

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

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

Multi-source replication
Source-replica replication

yes (replicated cache)

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

yes

yes (compute grid and hadoop accelerator)

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

atomic operations within a single document possible

ACID

can act as a resource manager in an XA/JTA transaction

Multi-item ACID transactions with snapshot isolation within a partition

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

yes, with Range Indexes

yes

User concepts

Access control

Access rights for users can be defined per database

Security Hooks for custom implementations

Role-based access control at the document and subdocument levels

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.