DBMS > Apache Druid vs. Couchbase vs. Riak KV

System Properties Comparison Apache Druid vs. Couchbase vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

Distributed, fault tolerant key-value store

Primary database model

Relational DBMS
Time Series DBMS

Document store

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

Score	17.30
Rank	#36	Overall
	#5	Document stores

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Website

druid.apache.org

www.couchbase.com

Technical documentation

druid.apache.org/docs/latest/design

docs.couchbase.com

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Apache Software Foundation and contributors

Couchbase, Inc.

OpenSource, formerly Basho Technologies

Initial release

2012

2011

2009

Current release

29.0.1, April 2024

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

3.2.0, December 2022

License

Commercial or Open Source

Open Source

Apache license v2

Open Source

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

Open Source

Apache version 2, commercial enterprise edition

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

Java

C, C++, Go and Erlang

Erlang

Server operating systems

Linux
OS X
Unix

Linux
OS X
Windows

Linux
OS X

Data scheme

yes

schema-less columns are supported

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

restricted

SQL

Support of SQL

SQL for querying

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

APIs and other access methods

JDBC
RESTful HTTP/JSON API

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

HTTP API
Native Erlang Interface

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

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

Erlang

Triggers

yes

via the TAP protocol

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Automatic Sharding

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

Multi-source replication

including cross data center replication
Source-replica replication

selectable replication factor

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

Eventual Consistency

Foreign keys

Referential integrity

links between data sets can be stored

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

In-memory capabilities

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

yes

Ephemeral buckets

User concepts

Access control

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

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

yes, using Riak Security

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.