DBMS > Faircom EDGE vs. Hypertable vs. MariaDB vs. MySQL vs. Trafodion

System Properties Comparison Faircom EDGE vs. Hypertable vs. MariaDB vs. MySQL vs. Trafodion

Editorial information provided by DB-Engines

Name

Hypertable has stopped its further development with March 2016 and is removed from the DB-Engines ranking.

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

Description

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

An open source BigTable implementation based on distributed file systems such as Hadoop

MySQL application compatible open source RDBMS, enhanced with high availability, security, interoperability and performance capabilities. MariaDB ColumnStore provides a column-oriented storage engine and MariaDB Xpand supports distributed SQL.

Widely used open source RDBMS

Transactional SQL-on-Hadoop DBMS

Primary database model

Key-value store
Relational DBMS

Wide column store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Secondary database models

Document store
Graph DBMS

with OQGraph storage engine
Spatial DBMS

Document store
Spatial DBMS

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

Score	0.02
Rank	#368	Overall
	#54	Key-value stores
	#156	Relational DBMS

Score	93.21
Rank	#13	Overall
	#9	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

www.faircom.com/products/faircom-edge

mariadb.com

Site of MariaDB Corporation
mariadb.org

Site of MariaDB Foundation

www.mysql.com

trafodion.apache.org

Technical documentation

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

mariadb.com/kb/en/library

dev.mysql.com/doc

trafodion.apache.org/documentation.html

Developer

FairCom Corporation

Hypertable Inc.

MariaDB Corporation Ab (MariaDB Enterprise),
MariaDB Foundation (community MariaDB Server)

The lead developer Monty Widenius is the original author of MySQL

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation, originally developed by HP

Initial release

1979

2009

Fork of MySQL, which was first released in 1995

1995

2014

Current release

V3, October 2020

0.9.8.11, March 2016

11.3.2, February 2024

8.4.0, April 2024

2.3.0, February 2019

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

GNU version 3. Commercial license available

Open Source

GPL version 2, commercial enterprise subscription available

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

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

STACKIT MariaDB offers MariaDB in a fully managed version in enterprise grade, 100% GDPR-compliant.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

ANSI C, C++

C++

C and C++

C++, Java

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

Linux
OS X
Windows

an inofficial Windows port is available

FreeBSD
Linux
Solaris
Windows

ColumnStore storage engine not available on Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

schema-free

yes

Dynamic columns are supported

yes

Typing

predefined data types such as float or date

yes, ANSI Standard SQL 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

restricted

only exact value or prefix value scans

yes

SQL

Support of SQL

yes

ANSI SQL queries

yes

with proprietary extensions

yes

with proprietary extensions

yes

APIs and other access methods

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

C++ API
Thrift

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
ODBC

Supported programming languages

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

C++
Java
Perl
PHP
Python
Ruby

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

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

yes

.Net, JavaScript, C/C++

yes

PL/SQL compatibility added with version 10.3

yes

proprietary syntax

Java Stored Procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning

Customizable business rules for partitioning

Sharding

several options for horizontal partitioning and Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

selectable replication factor on file system level

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
Tunable Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

not for MyISAM storage engine

yes

not for MyISAM storage engine

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

not for MyISAM storage engine

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

not for in-memory storage engine

yes

In-memory capabilities

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

yes

with MEMORY storage engine

yes

User concepts

Access control

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

fine grained access rights according to SQL-standard

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

Specific characteristics

MariaDB is the most powerful open source relational database – modern SQL and JSON...
» more

Competitive advantages

MariaDB Servers have many features unavailable in other open source relational databases....
» more

Typical application scenarios

Web, SaaS and Cloud operational applications that require high availability, scalability...
» more

Key customers

Deutsche Bank, DBS Bank, Nasdaq, Red Hat, ServiceNow, Verizon and Walgreens Featured...
» more

Market metrics

MariaDB is the default database in the LAMP stack supplied by Red Hat and SUSE Linux,...
» more

Licensing and pricing models

MariaDB plc subscriptions cover our free, open source database, Community Server,...
» more

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.