DBMS > Dgraph vs. Graph Engine vs. Microsoft Azure SQL Database vs. MySQL vs. Oracle Coherence

System Properties Comparison Dgraph vs. Graph Engine vs. Microsoft Azure SQL Database vs. MySQL vs. Oracle Coherence

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Database as a Service offering with high compatibility to Microsoft SQL Server

Widely used open source RDBMS

Oracles in-memory data grid solution

Primary database model

Graph DBMS

Graph DBMS
Key-value store

Relational DBMS

Key/Value like access via memcached API

Key-value store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	77.99
Rank	#16	Overall
	#11	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1.92
Rank	#130	Overall
	#22	Key-value stores

Website

dgraph.io

www.graphengine.io

azure.microsoft.com/en-us/products/azure-sql/database

www.mysql.com

www.oracle.com/java/coherence

Technical documentation

dgraph.io/docs

www.graphengine.io/docs/manual

docs.microsoft.com/en-us/azure/azure-sql

dev.mysql.com/doc

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

Developer

Dgraph Labs, Inc.

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

Initial release

2016

2010

1995

2007

Current release

V12

8.4.0, April 2024

14.1, August 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

MIT License

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

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

.NET and C

C++

C and C++

Java

Server operating systems

Linux
OS X
Windows

.NET

hosted

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Data scheme

schema-free

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

APIs and other access methods

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

RESTful HTTP API

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

JCache
JPA
RESTful HTTP API

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
C++
F#
Visual Basic

.Net
C#
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

.Net
C++
Java

Server-side scripts

Stored procedures

yes

Transact SQL

yes

proprietary syntax

Triggers

yes

Live Events

Partitioning methods

Methods for storing different data on different nodes

yes

horizontal partitioning

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

yes, with always 3 replicas available

Multi-source replication
Source-replica replication

yes, with selectable consistency level

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Transaction concepts

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

ACID

not for MyISAM storage engine

configurable

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

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

optionally

In-memory capabilities

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

yes

User concepts

Access control

Planned for future releases

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.