DBMS > Couchbase vs. Ehcache vs. Geode vs. KairosDB

System Properties Comparison Couchbase vs. Ehcache vs. Geode vs. KairosDB

Please select another system to include it in the comparison.

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

A widely adopted Java cache with tiered storage options

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Distributed Time Series DBMS based on Cassandra or H2

Primary database model

Document store

Key-value store

Time Series DBMS

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

Score	5.23
Rank	#68	Overall
	#8	Key-value stores

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	0.71
Rank	#230	Overall
	#20	Time Series DBMS

Website

www.couchbase.com

www.ehcache.org

geode.apache.org

github.com/kairosdb/kairosdb

Technical documentation

docs.couchbase.com

www.ehcache.org/documentation

geode.apache.org/docs

kairosdb.github.io

Developer

Couchbase, Inc.

Terracotta Inc, owned by Software AG

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Initial release

2011

2009

2002

2013

Current release

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

3.10.0, March 2022

1.1, February 2017

1.2.2, November 2018

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 Version 2; commercial licenses available as Gemfire

Open Source

Apache 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

Java

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Linux
OS X
Windows

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

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

SQL-like query language (OQL)

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

Java Client API
Memcached protocol
RESTful HTTP API

Graphite protocol
HTTP REST
Telnet API

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Java

.Net
All JVM based languages
C++
Groovy
Java
Scala

Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

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

user defined functions

Triggers

yes

via the TAP protocol

yes

Cache Event Listeners

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

Sharding

by using Terracotta Server

Sharding

based on Cassandra

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

Multi-source replication

selectable replication factor

based on Cassandra

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)

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

yes, on a single node

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 per client and object definable

simple password-based access control

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.