DBMS > BoltDB vs. CouchDB vs. MySQL vs. Postgres-XL vs. RocksDB

System Properties Comparison BoltDB vs. CouchDB vs. MySQL vs. Postgres-XL vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Widely used open source RDBMS

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Key-value store

Document store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Key-value store

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
Spatial DBMS

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

github.com/boltdb/bolt

Technical documentation

docs.couchdb.org/en/stable

dev.mysql.com/doc

www.postgres-xl.org/documentation

github.com/facebook/rocksdb/wiki

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Oracle

since 2010, originally MySQL AB, then Sun

Facebook, Inc.

Initial release

2013

2005

1995

2014

since 2012, originally named StormDB

2013

Current release

3.3.3, December 2023

8.4.0, April 2024

10 R1, October 2018

9.2.1, May 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Mozilla public license

Open Source

BSD

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

Erlang

C and C++

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Android
BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
macOS

Linux

Data scheme

schema-free

yes

schema-free

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

XML type, but no XML query functionality

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

distributed, parallel query execution

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

C++ API
Java API

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

View functions in JavaScript

yes

proprietary syntax

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

improved architecture with release 2.0

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

yes

atomic operations within a single document possible

ACID

not for MyISAM storage engine

ACID

MVCC

yes

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

table locks or row locks depending on storage engine

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.

yes

User concepts

Access control

Access rights for users can be defined per database

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard

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.