DBMS > Apache Impala vs. CockroachDB vs. CouchDB vs. Elasticsearch vs. MySQL

System Properties Comparison Apache Impala vs. CockroachDB vs. CouchDB vs. Elasticsearch vs. MySQL

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

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 native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

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

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Document store

Spatial DBMS

using the Geocouch extension

Document store
Spatial DBMS
Vector DBMS

Document store
Spatial DBMS

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

Score	14.03
Rank	#40	Overall
	#24	Relational DBMS

Score	6.10
Rank	#58	Overall
	#33	Relational DBMS

Score	10.26
Rank	#45	Overall
	#7	Document stores

Score	134.78
Rank	#7	Overall
	#1	Search engines

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Website

impala.apache.org

www.cockroachlabs.com

couchdb.apache.org

www.elastic.co/elasticsearch

www.mysql.com

Technical documentation

impala.apache.org/impala-docs.html

www.cockroachlabs.com/docs

docs.couchdb.org/en/stable

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

dev.mysql.com/doc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Cockroach Labs

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Elastic

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2013

2015

2005

2010

1995

Current release

4.1.0, June 2022

23.1.1, May 2023

3.3.3, December 2023

8.6, January 2023

8.3.0, January 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache 2.0, commercial license available

Open Source

Apache version 2

Open Source

Elastic License

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C++

Erlang

Java

C and C++

Server operating systems

Linux

Linux
macOS
Windows

Android
BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

dynamic schema

schema-free

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

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.

yes

Secondary indexes

yes

via views

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes, wire compatible with PostgreSQL

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

JDBC

RESTful HTTP/JSON API

Java API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

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

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
Groovy
Community Contributed Clients
Java
JavaScript
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

yes

user defined functions and integration of map-reduce

View functions in JavaScript

yes

proprietary syntax

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

improved architecture with release 2.0

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication using RAFT

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

ES-Hadoop Connector

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Eventual Consistency

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

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

atomic operations within a single document possible

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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.

Memcached and Redis integration

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Role-based access control

Access rights for users can be defined per database

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.