DBMS > Dgraph vs. Hazelcast vs. SAP HANA vs. TinkerGraph

System Properties Comparison Dgraph vs. Hazelcast vs. SAP HANA vs. TinkerGraph

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 widely adopted in-memory data grid

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

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	1.39
Rank	#155	Overall
	#15	Graph DBMS

Score	5.72
Rank	#59	Overall
	#6	Key-value stores

Score	41.32
Rank	#23	Overall
	#16	Relational DBMS

Score	0.08
Rank	#345	Overall
	#34	Graph DBMS

Website

dgraph.io

hazelcast.com

www.sap.com/products/hana.html

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

dgraph.io/docs

hazelcast.org/imdg/docs

help.sap.com/hana

Developer

Dgraph Labs, Inc.

Hazelcast

SAP

Initial release

2016

2008

2010

2009

Current release

5.3.6, November 2023

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Apache 2.0

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

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Appliance or cloud-service

Data scheme

schema-free

yes

schema-free

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

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

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

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
ODBC

TinkerPop 3

Supported programming languages

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

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

Groovy
Java

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

SQLScript, R

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

yes

Replicated Map

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

one or two-phase-commit; repeatable reads; read commited

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional

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

Role-based access control

yes

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.