DBMS > EsgynDB vs. MySQL vs. Realm vs. ToroDB vs. Trafodion

System Properties Comparison EsgynDB vs. MySQL vs. Realm vs. ToroDB vs. Trafodion

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

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

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Widely used open source RDBMS

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Transactional SQL-on-Hadoop DBMS

Primary database model

Relational DBMS

Key/Value like access via memcached API

Document store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	7.18
Rank	#52	Overall
	#8	Document stores

Website

www.esgyn.cn

www.mysql.com

realm.io

github.com/torodb/server

trafodion.apache.org

Technical documentation

dev.mysql.com/doc

realm.io/docs

trafodion.apache.org/documentation.html

Developer

Esgyn

Oracle

since 2010, originally MySQL AB, then Sun

Realm, acquired by MongoDB in May 2019

8Kdata

Apache Software Foundation, originally developed by HP

Initial release

2015

1995

2014

2016

2014

Current release

9.0.0, July 2024

2.3.0, February 2019

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

AGPL-V3

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.

Implementation language

C++, Java

C and C++

Java

C++, Java

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

Android
Backend: server-less
iOS
Windows

All OS with a Java 7 VM

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

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

.Net
Java

with Android only
Objective-C
React Native
Swift

All languages supporting JDBC/ODBC/ADO.Net

Server-side scripts

Stored procedures

Java Stored Procedures

yes

proprietary syntax

runs within the applications so server-side scripts are unnecessary

Java Stored Procedures

Triggers

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Multi-source replication
Source-replica replication

none

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

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

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

In-Memory realm

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

yes

Access rights for 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.