DBMS > CouchDB vs. MySQL vs. SAP HANA vs. Tarantool vs. WakandaDB

System Properties Comparison CouchDB vs. MySQL vs. SAP HANA vs. Tarantool vs. WakandaDB

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.

Widely used open source RDBMS

In-memory, column based data store. Available as appliance or cloud service

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Document store
Key-value store
Relational DBMS

Object oriented DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
Spatial DBMS

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	10.26
Rank	#45	Overall
	#7	Document stores

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	45.84
Rank	#22	Overall
	#16	Relational DBMS

Score	1.67
Rank	#150	Overall
	#25	Document stores
	#25	Key-value stores
	#69	Relational DBMS

Score	0.09
Rank	#352	Overall
	#16	Object oriented DBMS

Website

couchdb.apache.org

www.mysql.com

www.sap.com/products/hana.html

www.tarantool.io

wakanda.github.io

Technical documentation

docs.couchdb.org/en/stable

dev.mysql.com/doc

help.sap.com/hana

www.tarantool.io/en/doc

wakanda.github.io/doc

Developer

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

SAP

Wakanda SAS

Initial release

2005

1995

2010

2008

2012

Current release

3.3.3, December 2023

8.3.0, January 2024

2.0 SPS07 (April 4, 2023), April 2023

2.10.0, May 2022

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

Open Source

AGPLv3, extended commercial license available

Cloud-based only

Only available as a cloud service

also available as a cloud based 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

C and C++

C++, JavaScript

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Appliance or cloud-service

BSD
Linux
macOS

Linux
OS X
Windows

Data scheme

schema-free

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

with proprietary extensions

yes

Full-featured ANSI SQL support

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

Open binary protocol

RESTful HTTP API

Supported programming languages

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

JavaScript

Server-side scripts

Stored procedures

View functions in JavaScript

yes

proprietary syntax

SQLScript, R

Lua, C and SQL stored procedures

yes

Triggers

yes

yes, before/after data modification events, on replication events, client session events

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

yes

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

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

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

table locks or row locks depending on storage engine

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Access rights for users can be defined per database

Users with fine-grained authorization concept

no user groups or roles

yes

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

yes

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.