DBMS > CouchDB vs. HarperDB vs. Ignite vs. MySQL

System Properties Comparison CouchDB vs. HarperDB vs. Ignite vs. MySQL

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.

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

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

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	0.55
Rank	#248	Overall
	#38	Document stores

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

Technical documentation

docs.couchdb.org/en/stable

docs.harperdb.io/docs

apacheignite.readme.io/docs

dev.mysql.com/doc

Developer

Apache Software Foundation

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

HarperDB

Apache Software Foundation

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2005

2017

2015

1995

Current release

3.3.3, December 2023

3.1, August 2021

Apache Ignite 2.6

8.3.0, January 2024

License

Commercial or Open Source

Open Source

Apache version 2

commercial

free community edition available

Open Source

Apache 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

Erlang

Node.js

C++, Java, .Net

C and C++

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux
OS X

Linux
OS X
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

dynamic schema

yes

Typing

predefined data types such as float or date

yes

JSON data types

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 data manipulation statements

ANSI-99 for query and DML statements, subset of DDL

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP/JSON API

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

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
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

C#
C++
Java
PHP
Python
Ruby
Scala

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

Custom Functions

since release 3.1

yes (compute grid and cache interceptors can be used instead)

yes

proprietary syntax

Triggers

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

A table resides as a whole on one (or more) nodes in a cluster

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

the nodes on which a table resides can be defined

yes (replicated cache)

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

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

Atomic execution of specific operations

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

yes, using LMDB

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

Access rights for users and roles

Security Hooks for custom implementations

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.