DBMS > Couchbase vs. Datomic vs. MySQL vs. NuoDB vs. Oracle Berkeley DB

System Properties Comparison Couchbase vs. Datomic vs. MySQL vs. NuoDB vs. Oracle Berkeley DB

Editorial information provided by DB-Engines

Name

Description

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

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

Widely used open source RDBMS

NuoDB is a webscale distributed database that supports SQL and ACID transactions

Widely used in-process key-value store

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

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	17.30
Rank	#36	Overall
	#5	Document stores

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.89
Rank	#198	Overall
	#92	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Website

www.couchbase.com

www.datomic.com

www.mysql.com

www.3ds.com/nuodb-distributed-sql-database

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Couchbase, Inc.

Cognitect

Oracle

since 2010, originally MySQL AB, then Sun

Dassault Systèmes

originally NuoDB, Inc.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2011

2012

1995

2013

1994

Current release

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

1.0.6735, June 2023

8.4.0, April 2024

18.1.40, May 2020

License

Commercial or Open Source

Open Source

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

commercial

limited edition free

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

limited edition free

Open Source

commercial license 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

C, C++, Go and Erlang

Java, Clojure

C and C++

C++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

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

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

APIs and other access methods

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

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
ODBC

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Clojure
Java

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++
Go
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

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

yes

Transaction Functions

yes

proprietary syntax

Java, SQL

Triggers

yes

via the TAP protocol

By using transaction functions

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

none

But extensive use of caching in the application peers

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

data is dynamically stored/cached on the nodes where it is read/written

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

none

But extensive use of caching in the application peers

Multi-source replication
Source-replica replication

yes

Managed transparently by NuoDB

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

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

tunable commit protocol

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

MVCC

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

Ephemeral buckets

yes

recommended only for testing and development

yes

Temporary table

yes

User concepts

Access control

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

Users with fine-grained authorization concept

no user groups or roles

Standard SQL roles/ privileges, Administrative Users

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.