DBMS > HarperDB vs. IBM Cloudant vs. MySQL vs. Trafodion

System Properties Comparison HarperDB vs. IBM Cloudant vs. MySQL vs. Trafodion

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Apache Trafodion has been retired in 2021. Therefore it is excluded from the DB-Engines Ranking.

Description

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.

Database as a Service offering based on Apache CouchDB

Widely used open source RDBMS

Transactional SQL-on-Hadoop DBMS

Primary database model

Document store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.55
Rank	#252	Overall
	#38	Document stores

Score	2.73
Rank	#108	Overall
	#20	Document stores

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Website

www.harperdb.io

www.ibm.com/products/cloudant

www.mysql.com

trafodion.apache.org

Technical documentation

docs.harperdb.io/docs

cloud.ibm.com/docs/Cloudant

dev.mysql.com/doc

trafodion.apache.org/documentation.html

Developer

HarperDB

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation, originally developed by HP

Initial release

2017

2010

1995

2014

Current release

3.1, August 2021

8.3.0, January 2024

2.3.0, February 2019

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

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

Node.js

Erlang

C and C++

C++, Java

Server operating systems

Linux
OS X

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

dynamic schema

schema-free

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

SQL

Support of SQL

SQL-like data manipulation statements

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
ODBC

Supported programming languages

.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#
Java
JavaScript
Objective-C
PHP
Ruby

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

View functions (Map-Reduce) in JavaScript

yes

proprietary syntax

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

the nodes on which a table resides can be defined

Multi-source replication
Source-replica replication

yes, via HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via user defined functions and HBase

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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 execution of specific operations

atomic operations within a document possible

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

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

Access rights for users can be defined per database

Users with fine-grained authorization concept

no user groups or roles

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.