DBMS > BoltDB vs. MySQL vs. PouchDB vs. Tibero vs. XTDB

System Properties Comparison BoltDB vs. MySQL vs. PouchDB vs. Tibero vs. XTDB

Editorial information provided by DB-Engines

Name

Description

An embedded key-value store for Go.

Widely used open source RDBMS

JavaScript DBMS with an API inspired by CouchDB

A secure RDBMS, designed for easy portability from Oracle

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Key-value store

Relational DBMS

Key/Value like access via memcached API

Document store

Relational DBMS

Document store

Secondary database models

Document store
Spatial DBMS

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

Score	0.80
Rank	#215	Overall
	#31	Key-value stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	1.59
Rank	#148	Overall
	#68	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

github.com/boltdb/bolt

www.mysql.com

pouchdb.com

us.tmaxsoft.com/products/tibero

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

dev.mysql.com/doc

pouchdb.com/guides

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

www.xtdb.com/docs

Developer

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation

TmaxSoft

Juxt Ltd.

Initial release

2013

1995

2012

2003

2019

Current release

8.4.0, April 2024

7.1.1, June 2019

6, April 2015

1.19, September 2021

License

Commercial or Open Source

Open Source

MIT License

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

commercial

Open Source

MIT License

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

C and C++

JavaScript

C and Assembler

Clojure

Server operating systems

BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

server-less, requires a JavaScript environment (browser, Node.js)

AIX
HP-UX
Linux
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

via views

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

only for PouchDB Server
JavaScript API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

HTTP REST
JDBC

Supported programming languages

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

JavaScript

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Clojure
Java

Server-side scripts

Stored procedures

yes

proprietary syntax

View functions in JavaScript

Persistent Stored Procedure (PSM)

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

with a proxy-based framework, named couchdb-lounge

horizontal partitioning

by range, hash, list or composite

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Multi-source replication
Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

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

ACID

not for MyISAM storage engine

ACID

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

by using IndexedDB, WebSQL or LevelDB as backend

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

planned for next version

User concepts

Access control

Users with fine-grained authorization concept

no user groups or roles

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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.