DBMS > Couchbase vs. Dgraph vs. Ehcache vs. GeoMesa

System Properties Comparison Couchbase vs. Dgraph vs. Ehcache vs. GeoMesa

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

Distributed and scalable native Graph DBMS

A widely adopted Java cache with tiered storage options

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Primary database model

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

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Website

Technical documentation

docs.couchbase.com

dgraph.io/docs

www.ehcache.org/documentation

www.geomesa.org/documentation/stable/user/index.html

Developer

Couchbase, Inc.

Dgraph Labs, Inc.

Terracotta Inc, owned by Software AG

CCRi and others

Initial release

2011

2016

2009

2014

Current release

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

3.10.0, March 2022

5.0.0, May 2024

License

Commercial or Open Source

Open Source

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

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache License 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

Scala

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Data scheme

schema-free

yes

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

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

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

JCache

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

Java

Server-side scripts

Stored procedures

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

Triggers

yes

via the TAP protocol

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

yes

Sharding

by using Terracotta Server

depending on storage layer

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

Synchronous replication via Raft

yes

by using Terracotta Server

depending on storage layer

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

Tunable Consistency (Strong, Eventual, Weak)

depending on storage layer

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

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

depending on storage layer

User concepts

Access control

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

Planned for future releases

yes

depending on the DBMS used for storage

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.