DBMS > CouchDB vs. Microsoft Azure Cosmos DB vs. Quasardb vs. TerarkDB

System Properties Comparison CouchDB vs. Microsoft Azure Cosmos DB vs. Quasardb vs. TerarkDB

Please select another system to include it in the comparison.

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.

Globally distributed, horizontally scalable, multi-model database service

Distributed, high-performance timeseries database

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Time Series DBMS

Key-value 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	27.71
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.21
Rank	#322	Overall
	#29	Time Series DBMS

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

couchdb.apache.org

azure.microsoft.com/services/cosmos-db

quasar.ai

github.com/bytedance/terarkdb

Technical documentation

docs.couchdb.org/en/stable

learn.microsoft.com/azure/cosmos-db

doc.quasar.ai/master

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Apache Software Foundation

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

Microsoft

quasardb

ByteDance, originally Terark

Initial release

2005

2014

2009

2016

Current release

3.3.3, December 2023

3.14.1, January 2024

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Free community edition, Non-profit organizations and non-commercial usage are eligible for free licenses

commercial

restricted open source version 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

C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

hosted

BSD
Linux
OS X
Windows

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

integer and binary

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

via views

yes

All properties auto-indexed by default

yes

with tags

SQL

Support of SQL

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

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

HTTP API

C++ API
Java API

Supported programming languages

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

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

.Net
C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

C++
Java

Server-side scripts

Stored procedures

View functions in JavaScript

JavaScript

Triggers

yes

JavaScript

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

consistent hashing

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service

Source-replica replication with selectable replication factor

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate 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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

yes

by using LevelDB

yes

In-memory capabilities

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

yes

Transient mode

yes

User concepts

Access control

Access rights for users can be defined per database

Access rights can be defined down to the item level

Cryptographically strong user authentication and audit trail

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.