DBMS > Apache Drill vs. Couchbase vs. CouchDB vs. IRONdb vs. Oracle Berkeley DB

System Properties Comparison Apache Drill vs. Couchbase vs. CouchDB vs. IRONdb vs. Oracle Berkeley DB

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Widely used in-process key-value store

Primary database model

Document store
Relational DBMS

Document store

Time Series 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

Spatial DBMS

using the Geocouch extension

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

Score	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	9.30
Rank	#45	Overall
	#7	Document stores

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

Website

drill.apache.org

www.couchbase.com

couchdb.apache.org

www.circonus.com/solutions/time-series-database/

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

Technical documentation

drill.apache.org/docs

docs.couchbase.com

docs.couchdb.org/en/stable

docs.circonus.com/irondb/category/getting-started

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

Developer

Apache Software Foundation

Couchbase, Inc.

Apache Software Foundation

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

Circonus LLC.

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2012

2011

2005

2017

1994

Current release

1.20.3, January 2023

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

3.3.3, December 2023

V0.10.20, January 2018

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

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

Open Source

Apache version 2

commercial

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.

Implementation language

C, C++, Go and Erlang

Erlang

C and C++

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

Server operating systems

Linux
OS X
Windows

Android
BSD
Linux
OS X
Solaris
Windows

Linux

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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

via views

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

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

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

SQL interfaced based on SQLite is available

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

RESTful HTTP/JSON API

HTTP API

Supported programming languages

C++

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

.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

user defined functions

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

View functions in JavaScript

yes, in Lua

Triggers

yes

via the TAP protocol

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic Sharding

Sharding

improved architecture with release 2.0

Automatic, metric affinity per node

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Multi-source replication
Source-replica replication

configurable replication factor, datacenter aware

Source-replica replication

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

selectable on a per-operation basis

Eventual Consistency

Immediate consistency per node, eventual consistency across nodes

Foreign keys

Referential integrity

Transaction concepts

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

ACID

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

Ephemeral buckets

yes

User concepts

Access control

Depending on the underlying data source

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

Access rights for users can be defined per database

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.