DBMS > Amazon CloudSearch vs. Couchbase vs. Memcached vs. Vitess

System Properties Comparison Amazon CloudSearch vs. Couchbase vs. Memcached vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A hosted search engine service by Amazon with the data stored in Amazons cloud

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

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

Scalable, distributed, cloud-native DBMS, extending MySQL

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

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	1.81
Rank	#137	Overall
	#12	Search engines

Score	16.59
Rank	#36	Overall
	#5	Document stores

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

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

aws.amazon.com/cloudsearch

www.couchbase.com

www.memcached.org

vitess.io

Technical documentation

docs.aws.amazon.com/cloudsearch

docs.couchbase.com

github.com/memcached/memcached/wiki

vitess.io/docs

Developer

Amazon

Couchbase, Inc.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

The Linux Foundation, PlanetScale

Initial release

2012

2011

2003

2013

Current release

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

1.6.27, May 2024

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

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

Open Source

BSD license

Open Source

Apache Version 2.0, commercial licenses available

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

Server operating systems

hosted

Linux
OS X
Windows

FreeBSD
Linux
OS X
Unix
Windows

Docker
Linux
macOS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

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

yes

with proprietary extensions

APIs and other access methods

HTTP API

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

Proprietary protocol

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

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

yes

proprietary syntax

Triggers

yes

via the TAP protocol

yes

Partitioning methods

Methods for storing different data on different nodes

yes

automatic partitioning across Amazon Search Instance as required

Automatic Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

managed transparently by AWS

Multi-source replication

including cross data center replication
Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

Multi-source replication
Source-replica replication

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

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

yes

User concepts

Access control

authentication via encrypted signatures

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

yes

using SASL (Simple Authentication and Security Layer) protocol

Users with fine-grained authorization concept

no user groups or roles

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.