DBMS > Apache Drill vs. Couchbase vs. FoundationDB vs. MaxDB vs. Tkrzw

System Properties Comparison Apache Drill vs. Couchbase vs. FoundationDB vs. MaxDB vs. Tkrzw

Editorial information provided by DB-Engines

Name

Created as commercial project in 2013, FoundationDB has been acquired by Apple in March 2015 and was withdrawn from the market. As a consequence, the product was removed from the DB-Engines ranking. In April 2018, Apple open-sourced FoundationDB and it therefore reappears in the 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

Ordered key-value store. Core features are complimented by layers.

A robust and reliable RDBMS optimized to run all major SAP solutions

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Document store
Relational DBMS

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Relational DBMS

Key-value store

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

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	1.03
Rank	#190	Overall
	#31	Document stores
	#28	Key-value stores
	#89	Relational DBMS

Score	2.32
Rank	#112	Overall
	#55	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

drill.apache.org

www.couchbase.com

github.com/apple/foundationdb

maxdb.sap.com

dbmx.net/tkrzw

Technical documentation

drill.apache.org/docs

docs.couchbase.com

apple.github.io/foundationdb

maxdb.sap.com/documentation

Developer

Apache Software Foundation

Couchbase, Inc.

FoundationDB

SAP, acquired from Software AG (Adabas-D) in 1997

Mikio Hirabayashi

Initial release

2012

2011

2013

1984

2020

Current release

1.20.3, January 2023

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

6.2.28, November 2020

7.9.10.12, February 2024

0.9.3, August 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 2.0

commercial

Limited community edition free

Open Source

Apache Version 2.0

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

C++

Server operating systems

Linux
OS X
Windows

AIX
HP-UX
Linux
Solaris
Windows

Linux
macOS

Data scheme

schema-free

some layers support schemas

yes

schema-free

Typing

predefined data types such as float or date

yes

some layers support typing

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.

Secondary indexes

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

supported in specific SQL layer only

yes

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

ADO.NET
JDBC
ODBC
WebDAV

Supported programming languages

C++

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

.Net
C#
Java
Perl
PHP
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

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

in SQL-layer only

yes

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic Sharding

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

yes

Source-replica replication

none

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

Linearizable consistency

Immediate Consistency

Foreign keys

Referential integrity

in SQL-layer only

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

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

using specific database classes

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.

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.