DBMS > CouchDB vs. Elasticsearch vs. Infobright vs. MarkLogic vs. MySQL

System Properties Comparison CouchDB vs. Elasticsearch vs. Infobright vs. MarkLogic vs. MySQL

Editorial information provided by DB-Engines

Name

Description

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

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Operational and transactional Enterprise NoSQL database

Widely used open source RDBMS

Primary database model

Document store

Search engine

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Key/Value like access via memcached API

Secondary database models

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	9.30
Rank	#45	Overall
	#7	Document stores

Score	135.35
Rank	#7	Overall
	#1	Search engines

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

couchdb.apache.org

www.elastic.co/elasticsearch

ignitetech.com/softwarelibrary/infobrightdb

www.marklogic.com

www.mysql.com

Technical documentation

docs.couchdb.org/en/stable

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

docs.marklogic.com

dev.mysql.com/doc

Developer

Apache Software Foundation

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

Elastic

Ignite Technologies Inc.; formerly InfoBright Inc.

MarkLogic Corp.

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2005

2010

2005

2001

1995

Current release

3.3.3, December 2023

8.6, January 2023

11.0, December 2022

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Elastic License

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

restricted free version is available

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

Erlang

Java

C++

C and C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Linux
Windows

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

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

yes

schema-free

Schema can be enforced

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

SQL-like query language

yes

SQL92

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP/JSON API

Java API
RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C#
C++
Java
JavaScript (Node.js)
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

View functions in JavaScript

yes

via XQuery or JavaScript

yes

proprietary syntax

Triggers

yes

by using the 'percolation' feature

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

ES-Hadoop Connector

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

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

atomic operations within a single document possible

ACID

can act as a resource manager in an XA/JTA transaction

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

yes, with Range Indexes

yes

User concepts

Access control

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Role-based access control at the document and subdocument levels

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.