DBMS > BigchainDB vs. Dgraph vs. Ehcache vs. Microsoft Azure Cosmos DB

System Properties Comparison BigchainDB vs. Dgraph vs. Ehcache vs. Microsoft Azure Cosmos DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

Distributed and scalable native Graph DBMS

A widely adopted Java cache with tiered storage options

Globally distributed, horizontally scalable, multi-model database service

Primary database model

Document store

Graph DBMS

Key-value 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.85
Rank	#208	Overall
	#35	Document stores

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

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

Website

www.bigchaindb.com

dgraph.io

www.ehcache.org

azure.microsoft.com/services/cosmos-db

Technical documentation

bigchaindb.readthedocs.io/en/latest

dgraph.io/docs

www.ehcache.org/documentation

learn.microsoft.com/azure/cosmos-db

Developer

Dgraph Labs, Inc.

Terracotta Inc, owned by Software AG

Microsoft

Initial release

2016

2009

2014

Current release

3.10.0, March 2022

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses 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

Python

Java

Server operating systems

Linux

Linux
OS X
Windows

All OS with a Java VM

hosted

Data scheme

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

SQL-like query language

APIs and other access methods

CLI Client
RESTful HTTP API

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

JCache

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

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

Java

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

Server-side scripts

Stored procedures

JavaScript

Triggers

yes

Cache Event Listeners

JavaScript

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

by using Terracotta Server

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Synchronous replication via Raft

yes

by using Terracotta Server

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Tunable Consistency (Strong, Eventual, Weak)

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

ACID

yes

supports JTA and can work as an XA resource

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

using a tiered cache-storage approach

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

yes

Planned for future releases

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.