DBMS > Apache Impala vs. CouchDB vs. etcd vs. MySQL

System Properties Comparison Apache Impala vs. CouchDB vs. etcd vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

A distributed reliable key-value store

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

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

Score	14.03
Rank	#40	Overall
	#24	Relational DBMS

Score	10.26
Rank	#45	Overall
	#7	Document stores

Score	7.64
Rank	#54	Overall
	#5	Key-value stores

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Website

impala.apache.org

couchdb.apache.org

etcd.io
github.com/etcd-io/etcd

www.mysql.com

Technical documentation

impala.apache.org/impala-docs.html

docs.couchdb.org/en/stable

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

dev.mysql.com/doc

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Apache Software Foundation

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

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2013

2005

1995

Current release

4.1.0, June 2022

3.3.3, December 2023

3.4, August 2019

8.3.0, January 2024

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

Apache version 2

Open Source

Apache Version 2.0

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

C and C++

Server operating systems

Linux

Android
BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
Windows

experimental

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

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.

yes

Secondary indexes

yes

via views

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

gRPC
JSON over HTTP

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

All languages supporting JDBC/ODBC

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

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

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

yes, watching key changes

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

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
Source-replica replication

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

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.

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

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.