DBMS > Couchbase vs. Elasticsearch vs. Google Cloud Datastore vs. Kyligence Enterprise vs. Memcached

System Properties Comparison Couchbase vs. Elasticsearch vs. Google Cloud Datastore vs. Kyligence Enterprise vs. Memcached

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 distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A distributed analytics engine for big data, built on top of Apache Kylin

In-memory key-value store, originally intended for caching

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

Document store
Spatial 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	135.35
Rank	#7	Overall
	#1	Search engines

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.40
Rank	#269	Overall
	#124	Relational DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Website

www.couchbase.com

www.elastic.co/elasticsearch

cloud.google.com/datastore

kyligence.io/kyligence-enterprise

www.memcached.org

Technical documentation

docs.couchbase.com

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

cloud.google.com/datastore/docs

github.com/memcached/memcached/wiki

Developer

Couchbase, Inc.

Elastic

Google

Kyligence, Inc.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Initial release

2011

2010

2008

2016

2003

Current release

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

8.6, January 2023

1.6.27, May 2024

License

Commercial or Open Source

Open Source

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

Open Source

Elastic License

commercial

Open Source

BSD license

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

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

hosted

Linux

FreeBSD
Linux
OS X
Unix
Windows

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

All search fields are automatically indexed

yes

SQL

Support of SQL

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

SQL-like query language

SQL-like query language (GQL)

ANSI SQL for queries (using Apache Calcite)

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

Java API
RESTful HTTP/JSON API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC
RESTful HTTP API

Proprietary protocol

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

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

yes

using Google App Engine

Triggers

yes

via the TAP protocol

yes

by using the 'percolation' feature

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

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

Multi-source replication using Paxos

none

Repcached, a Memcached patch, provides this functionallity

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

ES-Hadoop Connector

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

yes

Ephemeral buckets

Memcached and Redis integration

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)

yes

using SASL (Simple Authentication and Security Layer) protocol

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.