DBMS > Dgraph vs. EJDB vs. MySQL vs. Qdrant vs. SAP Advantage Database Server

System Properties Comparison Dgraph vs. EJDB vs. MySQL vs. Qdrant vs. SAP Advantage Database Server

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Distributed and scalable native Graph DBMS

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

Widely used open source RDBMS

A high-performance vector database with neural network or semantic-based matching

Low-cost RDBMS with access to ISAM and FoxPro data structures

Primary database model

Graph DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Vector DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	1.28
Rank	#167	Overall
	#6	Vector DBMS

Website

dgraph.io

github.com/Softmotions/ejdb

www.mysql.com

github.com/qdrant/qdrant
qdrant.tech

www.sap.com/products/advantage-database-server.html

Technical documentation

dgraph.io/docs

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

dev.mysql.com/doc

qdrant.tech/documentation

Developer

Dgraph Labs, Inc.

Softmotions

Oracle

since 2010, originally MySQL AB, then Sun

Qdrant

Sybase, SAP

Initial release

2016

2012

1995

2021

1993

Current release

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPLv2

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache Version 2.0

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

Rust

Server operating systems

Linux
OS X
Windows

server-less

FreeBSD
Linux
OS X
Solaris
Windows

Docker
Linux
macOS
Windows

Linux
Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

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

in-process shared library

ADO.NET
JDBC
ODBC
Proprietary native API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

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

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

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Delphi
Perl
PHP

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

none

Multi-source replication
Source-replica replication

Collection-level replication

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
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

Eventual Consistency, tunable consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

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

Read/Write Locking

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

caching of (temporary) tables can be configured

User concepts

Access control

Planned for future releases

Users with fine-grained authorization concept

no user groups or roles

Key-based authentication

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.