DBMS > Dgraph vs. MySQL vs. SAP Adaptive Server vs. TerminusDB

System Properties Comparison Dgraph vs. MySQL vs. SAP Adaptive Server vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Widely used open source RDBMS

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Graph DBMS

Relational DBMS

Key/Value like access via memcached API

Relational DBMS

Graph DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Boeing's Spatial Query Server

Document store
RDF store

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

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	35.09
Rank	#25	Overall
	#17	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

dgraph.io

www.mysql.com

www.sap.com/products/technology-platform/sybase-ase.html

terminusdb.com

Technical documentation

dgraph.io/docs

dev.mysql.com/doc

help.sap.com/docs/SAP_ASE

terminusdb.github.io/terminusdb/#

Developer

Dgraph Labs, Inc.

Oracle

since 2010, originally MySQL AB, then Sun

SAP, Sybase

DataChemist Ltd.

Initial release

2016

1995

1987

2018

Current release

8.4.0, April 2024

16.0

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

AIX
HP-UX
Linux
Solaris
Unix
Windows

Linux

Data scheme

schema-free

yes

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

SQL-like query language (WOQL)

APIs and other access methods

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

ADO.NET
JDBC
ODBC
Proprietary native API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C#
C++
Go
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

C
C++
Cobol
Java
Java
Perl
PHP
Python

JavaScript
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

Java and Transact-SQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication
Source-replica replication

Journaling Streams

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

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

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

in-memory journaling

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

fine grained access rights according to SQL-standard

Role-based access control

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.