DBMS > CouchDB vs. MySQL vs. OpenQM vs. Teradata

System Properties Comparison CouchDB vs. MySQL vs. OpenQM vs. Teradata

Please select another system to include it in the comparison.

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

QpenQM is a high-performance, self-tuning, multi-value DBMS

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Multivalue DBMS

Relational DBMS

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
Spatial DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	7.46
Rank	#51	Overall
	#7	Document stores

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.28
Rank	#291	Overall
	#10	Multivalue DBMS

Score	41.47
Rank	#22	Overall
	#15	Relational DBMS

Website

couchdb.apache.org

www.mysql.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.teradata.com

Technical documentation

docs.couchdb.org/en/stable

dev.mysql.com/doc

docs.teradata.com

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

Rocket Software, originally Martin Phillips

Teradata

Initial release

2005

1995

1993

1984

Current release

3.3.3, December 2023

9.0.0, July 2024

3.4-12

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPLv2, extended commercial license available

commercial

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.

Implementation language

Erlang

C and C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

hosted
Linux

Data scheme

schema-free

yes

with some exceptions

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

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL 2016 + extensions

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

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

.Net
Basic
C
Java
Objective C
PHP
Python

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

View functions in JavaScript

yes

proprietary syntax

yes

UDFs, stored procedures, table functions in parallel

Triggers

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

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Multi-source replication
Source-replica replication

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

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

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

table locks or row locks depending on storage engine

yes

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 can be defined per database

Users with fine-grained authorization concept

no user groups or roles

Access rights can be defined down to the item level

fine grained access rights according to SQL-standard

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.