DBMS > Badger vs. BigchainDB vs. Microsoft Access vs. MySQL vs. OpenTSDB

System Properties Comparison Badger vs. BigchainDB vs. Microsoft Access vs. MySQL vs. OpenTSDB

Editorial information provided by DB-Engines

Name

Description

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

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

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Widely used open source RDBMS

Scalable Time Series DBMS based on HBase

Primary database model

Key-value store

Document store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.22
Rank	#320	Overall
	#47	Key-value stores

Score	0.85
Rank	#208	Overall
	#35	Document stores

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.68
Rank	#142	Overall
	#12	Time Series DBMS

Website

github.com/dgraph-io/badger

www.bigchaindb.com

www.microsoft.com/en-us/microsoft-365/access

www.mysql.com

opentsdb.net

Technical documentation

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

bigchaindb.readthedocs.io/en/latest

developer.microsoft.com/en-us/access

dev.mysql.com/doc

opentsdb.net/docs/build/html/index.html

Developer

DGraph Labs

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

currently maintained by Yahoo and other contributors

Initial release

2017

2016

1992

1995

2011

Current release

1902 (16.0.11328.20222), March 2019

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

AGPL v3

commercial

Bundled with Microsoft Office

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

LGPL

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

Java

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Linux

Windows

Not a real database server, but making use of DLLs

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

numeric data for metrics, strings for tags

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

yes

but not compliant to any SQL standard

yes

with proprietary extensions

APIs and other access methods

CLI Client
RESTful HTTP API

ADO.NET
DAO
ODBC
OLE DB

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP API
Telnet API

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

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

Erlang
Go
Java
Python
R
Ruby

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

yes

proprietary syntax

Triggers

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

none

Multi-source replication
Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

but no files for transaction logging

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

yes,with MongoDB ord RethinkDB

yes

but no files for transaction logging

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

a simple user-level security was built in till version Access 2003

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.