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

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

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

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

Database as a Service offering based on Apache CouchDB

Distributed Event Store optimized for Internet of Things use cases

Globally distributed, horizontally scalable, multi-model database service

Adaptable, secure NoSQL built on Apache Accumulo

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

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	0.19
Rank	#323	Overall
	#2	Event Stores
	#28	Time Series DBMS

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

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

azure.microsoft.com/services/cosmos-db

sqrrl.com

Technical documentation

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

cloud.ibm.com/docs/Cloudant

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

learn.microsoft.com/azure/cosmos-db

Developer

DGraph Labs

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

IBM

Microsoft

Amazon

originally Sqrrl Data, Inc.

Initial release

2017

2010

2017

2014

2012

Current release

2.0

License

Commercial or Open Source

Open Source

Apache 2.0

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

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

Linux

Linux, macOS, Windows for the developer addition

hosted

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

JSON types

yes

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

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

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

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

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes

JavaScript

Triggers

yes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

Sharding

making use of Hadoop

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

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

yes

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

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Foreign keys

Referential integrity

Transaction concepts

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

atomic operations within a document possible

Multi-item ACID transactions with snapshot isolation within a partition

Atomic updates per row, document, or graph entity

Concurrency

Support for concurrent manipulation of data

yes

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

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.