DBMS > Dgraph vs. HarperDB vs. Ingres vs. MySQL

System Properties Comparison Dgraph vs. HarperDB vs. Ingres 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

Ultra-low latency distributed database with an intuitive REST API supporting NoSQL and SQL (including joins). Deployment of functions and databases simultaneously with a consolidated node-level architecture.

Well established RDBMS

Widely used open source RDBMS

Primary database model

Graph DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Secondary database models

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.55
Rank	#248	Overall
	#38	Document stores

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

dgraph.io

www.harperdb.io

www.actian.com/databases/ingres

www.mysql.com

Technical documentation

dgraph.io/docs

docs.harperdb.io/docs

docs.actian.com/ingres

dev.mysql.com/doc

Developer

Dgraph Labs, Inc.

HarperDB

Actian Corporation

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2016

2017

1974

originally developed at University Berkely in early 1970s

1995

Current release

3.1, August 2021

11.2, May 2022

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

free community edition available

commercial

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

Node.js

C and C++

Server operating systems

Linux
OS X
Windows

Linux
OS X

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

dynamic schema

yes

Typing

predefined data types such as float or date

yes

JSON data 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.

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like data manipulation statements

yes

with proprietary extensions

APIs and other access methods

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

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

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

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

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

Custom Functions

since release 3.1

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

A table resides as a whole on one (or more) nodes in a cluster

horizontal partitioning

Ingres Star to access multiple databases simultaneously

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

yes

the nodes on which a table resides can be defined

Ingres Replicator

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

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Atomic execution of specific operations

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

yes

yes, using LMDB

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

Access rights for users and roles

fine grained access rights according to SQL-standard

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.