DBMS > Dgraph vs. Microsoft Azure Cosmos DB vs. MySQL vs. Oracle vs. Oracle Berkeley DB

System Properties Comparison Dgraph vs. Microsoft Azure Cosmos DB vs. MySQL vs. Oracle vs. Oracle Berkeley DB

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Globally distributed, horizontally scalable, multi-model database service

Widely used open source RDBMS

Widely used RDBMS

Widely used in-process key-value store

Primary database model

Graph DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Secondary database models

Spatial DBMS

Document store
Spatial DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Website

dgraph.io

azure.microsoft.com/services/cosmos-db

www.mysql.com

www.oracle.com/database

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

dgraph.io/docs

learn.microsoft.com/azure/cosmos-db

dev.mysql.com/doc

docs.oracle.com/en/database

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Dgraph Labs, Inc.

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

2016

2014

1995

1980

1994

Current release

8.4.0, April 2024

23c, September 2023

18.1.40, May 2020

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

restricted free version is available

Open Source

commercial license available

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

C and C++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

Linux
OS X
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

schema-free

Typing

predefined data types such as float or date

yes

JSON 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

only with the Berkeley DB XML edition

Secondary indexes

yes

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

APIs and other access methods

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

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

JavaScript

yes

proprietary syntax

PL/SQL

also stored procedures in Java possible

Triggers

JavaScript

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session 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

Multi-item ACID transactions with snapshot isolation within a partition

ACID

not for MyISAM storage engine

ACID

isolation level can be parameterized

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

Planned for future releases

Access rights can be defined down to the item level

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

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.