DBMS > EsgynDB vs. MySQL vs. NuoDB vs. Oracle Coherence

System Properties Comparison EsgynDB vs. MySQL vs. NuoDB vs. Oracle Coherence

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Widely used open source RDBMS

NuoDB is a webscale distributed database that supports SQL and ACID transactions

Oracles in-memory data grid solution

Primary database model

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Key-value store

Secondary database models

Document store
Spatial DBMS

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

Score	0.23
Rank	#319	Overall
	#141	Relational DBMS

Score	1087.72
Rank	#2	Overall
	#2	Relational DBMS

Score	0.99
Rank	#195	Overall
	#92	Relational DBMS

Score	2.02
Rank	#131	Overall
	#22	Key-value stores

Website

www.esgyn.cn

www.mysql.com

www.3ds.com/nuodb-distributed-sql-database

www.oracle.com/java/coherence

Technical documentation

dev.mysql.com/doc

doc.nuodb.com

docs.oracle.com/en/middleware/standalone/coherence

Developer

Esgyn

Oracle

since 2010, originally MySQL AB, then Sun

Dassault Systèmes

originally NuoDB, Inc.

Oracle

Initial release

2015

1995

2013

2007

Current release

8.3.0, January 2024

14.1, August 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

limited edition free

commercial

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

C++, Java

C and C++

C++

Java

Server operating systems

Linux

FreeBSD
Linux
OS X
Solaris
Windows

hosted

Amazon EC2, Windows Azure, SoftLayer
Linux
OS X
Windows

All OS with a Java VM

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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

JCache
JPA
RESTful HTTP API

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
C
C++
Go
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C++
Java

Server-side scripts

Stored procedures

Java Stored Procedures

yes

proprietary syntax

Java, SQL

Triggers

yes

Live Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

data is dynamically stored/cached on the nodes where it is read/written

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

Multi-source replication
Source-replica replication

yes

Managed transparently by NuoDB

yes, with selectable consistency level

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

ACID

not for MyISAM storage engine

ACID

tunable commit protocol

configurable

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

MVCC

yes

Durability

Support for making data persistent

yes

optionally

In-memory capabilities

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

yes

Temporary table

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

Standard SQL roles/ privileges, Administrative Users

authentification to access the cache via certificates or http basic authentication

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.