DBMS > Badger vs. Drizzle vs. IBM Cloudant vs. Microsoft Azure Cosmos DB

System Properties Comparison Badger vs. Drizzle vs. IBM Cloudant vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Database as a Service offering based on Apache CouchDB

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Key-value store

Relational DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Spatial DBMS

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

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

Score	2.68
Rank	#106	Overall
	#20	Document stores

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

Website

github.com/dgraph-io/badger

www.ibm.com/products/cloudant

azure.microsoft.com/services/cosmos-db

Technical documentation

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

cloud.ibm.com/docs/Cloudant

learn.microsoft.com/azure/cosmos-db

Developer

DGraph Labs

Drizzle project, originally started by Brian Aker

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Microsoft

Initial release

2017

2008

2010

2014

Current release

7.2.4, September 2012

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GNU GPL

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

C++

Erlang

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X

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

All properties auto-indexed by default

SQL

Support of SQL

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

JDBC

RESTful HTTP/JSON API

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

Supported programming languages

C
C++
Java
PHP

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

JavaScript

Triggers

hooks for callbacks inside the server can be used.

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica 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

yes

Transaction concepts

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

ACID

atomic operations within a document possible

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users can be defined per database

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.