DBMS > Amazon DocumentDB vs. CouchDB vs. LeanXcale vs. Linter vs. MySQL

System Properties Comparison Amazon DocumentDB vs. CouchDB vs. LeanXcale vs. Linter vs. MySQL

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

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

A highly scalable full ACID SQL database with fast NoSQL data ingestion and GIS capabilities

RDBMS for high security requirements

Widely used open source RDBMS

Primary database model

Document store

Key-value store
Relational DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Spatial DBMS

using the Geocouch extension

Spatial DBMS

Document store
Spatial DBMS

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

Score	1.89
Rank	#137	Overall
	#24	Document stores

Score	10.26
Rank	#45	Overall
	#7	Document stores

Score	0.35
Rank	#283	Overall
	#41	Key-value stores
	#128	Relational DBMS

Score	0.10
Rank	#350	Overall
	#153	Relational DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Website

aws.amazon.com/documentdb

Technical documentation

aws.amazon.com/documentdb/resources

docs.couchdb.org/en/stable

dev.mysql.com/doc

Developer

Apache Software Foundation

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

LeanXcale

relex.ru

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2019

2005

2015

1990

1995

Current release

3.3.3, December 2023

8.3.0, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache version 2

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Cloud-based only

Only available as a cloud service

yes

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

C and C++

Server operating systems

hosted

Android
BSD
Linux
OS X
Solaris
Windows

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

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

yes

through Apache Derby

yes

with proprietary extensions

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

RESTful HTTP/JSON API

JDBC
Kafka Connector
ODBC
proprietary key/value interface
Spark Connector

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

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

C
Java
Scala

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
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

View functions in JavaScript

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

improved architecture with release 2.0

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

Multi-source replication
Source-replica replication

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic single-document operations

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 and roles

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

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.