DBMS > Couchbase vs. Ehcache vs. FoundationDB vs. Google Cloud Bigtable

System Properties Comparison Couchbase vs. Ehcache vs. FoundationDB vs. Google Cloud Bigtable

Please select another system to include it in the comparison.

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

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

A widely adopted Java cache with tiered storage options

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

Primary database model

Document store

Key-value store

Document store

supported via specific layer
Key-value store
Relational DBMS

supported via specific SQL-layer

Key-value store
Wide column 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	17.30
Rank	#36	Overall
	#5	Document stores

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	1.03
Rank	#190	Overall
	#31	Document stores
	#28	Key-value stores
	#89	Relational DBMS

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Website

www.couchbase.com

www.ehcache.org

github.com/apple/foundationdb

cloud.google.com/bigtable

Technical documentation

docs.couchbase.com

www.ehcache.org/documentation

apple.github.io/foundationdb

cloud.google.com/bigtable/docs

Developer

Couchbase, Inc.

Terracotta Inc, owned by Software AG

FoundationDB

Google

Initial release

2011

2009

2013

2015

Current release

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

3.10.0, March 2022

6.2.28, November 2020

License

Commercial or Open Source

Open Source

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

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

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

Java

C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Linux
OS X
Windows

hosted

Data scheme

schema-free

some layers support schemas

schema-free

Typing

predefined data types such as float or date

yes

some layers support typing

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++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

supported in specific SQL layer only

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

JCache

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Java

.Net
C
C++
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Swift

C#
C++
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

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

in SQL-layer only

Triggers

yes

via the TAP protocol

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

Sharding

by using Terracotta Server

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

yes

by using Terracotta Server

yes

Internal replication in Colossus, and regional replication between two clusters in different zones

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

Tunable Consistency (Strong, Eventual, Weak)

Linearizable consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Foreign keys

Referential integrity

in SQL-layer only

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

ACID

Atomic single-row operations

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

In-memory capabilities

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

yes

Ephemeral buckets

yes

User concepts

Access control

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.