DBMS > CockroachDB vs. Couchbase vs. Memcached vs. Sadas Engine vs. Sphinx

System Properties Comparison CockroachDB vs. Couchbase vs. Memcached vs. Sadas Engine vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

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

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Open source search engine for searching in data from different sources, e.g. relational databases

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	5.73
Rank	#58	Overall
	#34	Relational DBMS

Score	16.59
Rank	#36	Overall
	#5	Document stores

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

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

www.cockroachlabs.com

Technical documentation

www.cockroachlabs.com/docs

docs.couchbase.com

github.com/memcached/memcached/wiki

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

sphinxsearch.com/docs

Developer

Cockroach Labs

Couchbase, Inc.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

SADAS s.r.l.

Sphinx Technologies Inc.

Initial release

2015

2011

2003

2006

2001

Current release

24.1.0, May 2024

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

1.6.27, May 2024

8.0

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

Open Source

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

Open Source

BSD license

commercial

free trial version available

Open Source

GPL version 2, commercial licence available

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

C++

Server operating systems

Linux
macOS
Windows

Linux
OS X
Windows

FreeBSD
Linux
OS X
Unix
Windows

AIX
Linux
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

dynamic schema

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

full-text index on all search fields

SQL

Support of SQL

yes, wire compatible with PostgreSQL

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

yes

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC

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

Proprietary protocol

JDBC
ODBC
Proprietary protocol

Proprietary protocol

Supported programming languages

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

.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

.Net
C
C#
C++
Groovy
Java
PHP
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

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

Triggers

yes

via the TAP protocol

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

Automatic Sharding

none

horizontal partitioning

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

Multi-source replication

including cross data center replication
Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

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

yes

Ephemeral buckets

yes

managed by 'Learn by Usage'

User concepts

Access control

Role-based access control

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

yes

using SASL (Simple Authentication and Security Layer) protocol

Access rights for users, groups and roles according to SQL-standard

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.