DBMS > Dgraph vs. Oracle NoSQL vs. SAP HANA vs. TerminusDB

System Properties Comparison Dgraph vs. Oracle NoSQL vs. SAP HANA 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

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

In-memory, column based data store. Available as appliance or cloud service

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

Primary database model

Graph DBMS

Document store
Key-value store
Relational DBMS

Relational DBMS

Graph DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

dgraph.io

www.oracle.com/database/nosql/technologies/nosql

www.sap.com/products/hana.html

terminusdb.com

Technical documentation

dgraph.io/docs

docs.oracle.com/en/database/other-databases/nosql-database/index.html

help.sap.com/hana

terminusdb.github.io/terminusdb/#

Developer

Dgraph Labs, Inc.

Oracle

SAP

DataChemist Ltd.

Initial release

2016

2011

2010

2018

Current release

24.1, May 2024

2.0 SPS07 (April 4, 2023), April 2023

11.0.0, January 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

commercial

Open Source

GPL V3

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

Prolog, Rust

Server operating systems

Linux
OS X
Windows

Linux
Solaris SPARC/x86

Appliance or cloud-service

Linux

Data scheme

schema-free

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

Typing

predefined data types such as float or date

yes

optional

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-like query language (WOQL)

APIs and other access methods

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

RESTful HTTP API

JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

C
C#
Go
Java
JavaScript (Node.js)
Python

JavaScript
Python

Server-side scripts

Stored procedures

SQLScript, R

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

yes

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

configurable

ACID within a storage node (=shard)

ACID

Concurrency

Support for concurrent manipulation of data

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

off heap cache

yes

User concepts

Access control

Planned for future releases

Access rights for users and roles

yes

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.