DBMS > Dgraph vs. EJDB vs. Immudb vs. MySQL

System Properties Comparison Dgraph vs. EJDB vs. Immudb vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Relational 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.27
Rank	#297	Overall
	#44	Document stores

Score	0.24
Rank	#305	Overall
	#43	Key-value stores

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

dgraph.io

github.com/Softmotions/ejdb

github.com/codenotary/immudb
immudb.io

www.mysql.com

Technical documentation

dgraph.io/docs

github.com/Softmotions/ejdb/blob/master/README.md

docs.immudb.io

dev.mysql.com/doc

Developer

Dgraph Labs, Inc.

Softmotions

Codenotary

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2016

2012

2020

1995

Current release

1.2.3, April 2022

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPLv2

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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 and C++

Server operating systems

Linux
OS X
Windows

server-less

BSD
Linux
macOS
Solaris
Windows
z/OS

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, 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

SQL-like syntax

yes

with proprietary extensions

APIs and other access methods

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

in-process shared library

gRPC protocol
PostgreSQL wire protocol

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

none

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

none

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

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

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

Planned for future releases

Users with fine-grained authorization concept

no user groups or roles

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.