DBMS > HBase vs. MySQL vs. OpenEdge vs. Tarantool vs. Trafodion

System Properties Comparison HBase vs. MySQL vs. OpenEdge vs. Tarantool vs. Trafodion

Editorial information provided by DB-Engines

Name

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

Description

Wide-column store based on Apache Hadoop and on concepts of BigTable

Widely used open source RDBMS

Application development environment with integrated database management system

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

Transactional SQL-on-Hadoop DBMS

Primary database model

Wide column store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	30.50
Rank	#26	Overall
	#2	Wide column stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

hbase.apache.org

www.mysql.com

www.progress.com/openedge

www.tarantool.io

trafodion.apache.org

Technical documentation

hbase.apache.org/book.html

dev.mysql.com/doc

documentation.progress.com/output/ua/OpenEdge_latest

www.tarantool.io/en/doc

trafodion.apache.org/documentation.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Powerset

Oracle

since 2010, originally MySQL AB, then Sun

Progress Software Corporation

Apache Software Foundation, originally developed by HP

Initial release

2008

1995

1984

2008

2014

Current release

2.3.4, January 2021

8.4.0, April 2024

OpenEdge 12.2, March 2020

2.10.0, May 2022

2.3.0, February 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

Apache 2.0

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

Java

C and C++

C++, Java

Server operating systems

Linux
Unix
Windows

using Cygwin

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Windows

BSD
Linux
macOS

Linux

Data scheme

schema-free, schema definition possible

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

options to bring your own types, AVRO

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

SQL

Support of SQL

yes

with proprietary extensions

yes

close to SQL 92

Full-featured ANSI SQL support

yes

APIs and other access methods

Java API
RESTful HTTP API
Thrift

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

Open binary protocol

ADO.NET
JDBC
ODBC

Supported programming languages

C
C#
C++
Groovy
Java
PHP
Python
Scala

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

Progress proprietary ABL (Advanced Business Language)

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

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

yes

Coprocessors in Java

yes

proprietary syntax

yes

Lua, C and SQL stored procedures

Java Stored Procedures

Triggers

yes

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

since Version 11.4

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

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

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 or 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

Single row ACID (across millions of columns)

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

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 Control Lists (ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC

Users with fine-grained authorization concept

no user groups or roles

Users and groups

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

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.