DBMS > Badger vs. CouchDB vs. IBM Db2 Event Store vs. Microsoft Azure Cosmos DB

System Properties Comparison Badger vs. CouchDB vs. IBM Db2 Event Store vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Distributed Event Store optimized for Internet of Things use cases

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Key-value store

Document store

Event Store
Time Series DBMS

Document store
Graph DBMS
Key-value store
Wide column 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	0.14
Rank	#328	Overall
	#48	Key-value stores

Score	7.46
Rank	#51	Overall
	#7	Document stores

Score	0.18
Rank	#315	Overall
	#2	Event Stores
	#26	Time Series DBMS

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

Website

github.com/dgraph-io/badger

couchdb.apache.org

www.ibm.com/products/db2-event-store

azure.microsoft.com/services/cosmos-db

Technical documentation

godoc.org/github.com/dgraph-io/badger

docs.couchdb.org/en/stable

www.ibm.com/docs/en/db2-event-store

learn.microsoft.com/azure/cosmos-db

Developer

DGraph Labs

Apache Software Foundation

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

IBM

Microsoft

Initial release

2017

2005

2017

2014

Current release

3.3.3, December 2023

2.0

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache version 2

commercial

free developer edition available

commercial

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

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Android
BSD
Linux
OS X
Solaris
Windows

Linux

Linux, macOS, Windows for the developer addition

hosted

Data scheme

schema-free

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

via views

yes

All properties auto-indexed by default

SQL

Support of SQL

yes

through the embedded Spark runtime

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table 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#
C++
Cobol
Delphi
Fortran
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Scala
Visual Basic

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

Server-side scripts

Stored procedures

View functions in JavaScript

yes

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

improved architecture with release 2.0

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Active-active shard replication

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

No - written data is immutable

yes

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

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 can be defined per database

fine grained access rights according to SQL-standard

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.