DBMS > BigchainDB vs. Couchbase vs. Dgraph vs. MySQL

System Properties Comparison BigchainDB vs. Couchbase vs. Dgraph vs. MySQL

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

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

Distributed and scalable native Graph DBMS

Widely used open source RDBMS

Primary database model

Document store

Graph DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

Document store
Spatial DBMS

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

Technical documentation

bigchaindb.readthedocs.io/en/latest

docs.couchbase.com

dgraph.io/docs

dev.mysql.com/doc

Developer

Couchbase, Inc.

Dgraph Labs, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2016

2011

2016

1995

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

8.4.0, April 2024

License

Commercial or Open Source

Open Source

AGPL v3

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Python

C, C++, Go and Erlang

C and C++

Server operating systems

Linux

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

yes

with proprietary extensions

APIs and other access methods

CLI Client
RESTful HTTP API

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

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

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

yes

proprietary syntax

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic Sharding

yes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

including cross data center replication
Source-replica replication

Synchronous replication via Raft

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

yes

In-memory capabilities

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

yes

Ephemeral buckets

yes

User concepts

Access control

yes

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

Planned for future releases

Users with fine-grained authorization concept

no user groups or roles

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.