DBMS > Apache Drill vs. Couchbase vs. Elasticsearch

System Properties Comparison Apache Drill vs. Couchbase vs. Elasticsearch

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

A distributed document store with a powerful search engine and in-built operational and analytical capabilities

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

Primary database model

Document store
Relational DBMS

Document store

Search engine

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension

Document store
Spatial DBMS
Vector DBMS

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

Score	3.14
Rank	#114	Overall
	#22	Document stores
	#58	Relational DBMS

Score	25.34
Rank	#31	Overall
	#5	Document stores

Score	143.75
Rank	#8	Overall
	#1	Search engines

Website

drill.apache.org

www.couchbase.com

www.elastic.co/elasticsearch

Technical documentation

drill.apache.org/docs

docs.couchbase.com

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

Developer

Apache Software Foundation

Couchbase, Inc.

Elastic

Initial release

2012

2011

2010

Current release

1.20.3, January 2023

Server: 7.0, July 2021; Mobile: 3, February 2022; Couchbase Capella, October 2021

8.6, January 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache version 2; Commercial licenses also available

Open Source

Elastic License

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

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Data scheme

schema-free

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

Typing

predefined data types such as float or date

yes

String, Boolean, Number

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

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

Declarative query language (N1QL) that extends ANSI SQL to JSON. First commercial implementation of SQL++.

SQL-like query language

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Native language bindings for CRUD, Query, Search and Analytics APIs

Java API
RESTful HTTP/JSON API

Supported programming languages

C++

.Net
C
Go
Java
JavaScript

Node.js
PHP
Python
Ruby
Scala

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

Server-side scripts

Stored procedures

user defined functions

Functions and timers in JavaScript

yes

Triggers

yes

via the TAP protocol

yes

by using the 'percolation' feature

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

none

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

Foreign keys

Referential integrity

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

Depending on the underlying data source

yes

In-memory capabilities

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

Depending on the underlying data source

yes

Ephemeral buckets

Memcached and Redis integration

User concepts

Access control

Depending on the underlying data source

User and Administrator separation with password-based and LDAP integrated Authentication

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.