DBMS > Dgraph vs. Hazelcast vs. Oracle vs. SwayDB

System Properties Comparison Dgraph vs. Hazelcast vs. Oracle vs. SwayDB

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

Widely used RDBMS

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Website

dgraph.io

hazelcast.com

www.oracle.com/database

swaydb.simer.au

Technical documentation

dgraph.io/docs

hazelcast.org/imdg/docs

docs.oracle.com/en/database

Developer

Dgraph Labs, Inc.

Hazelcast

Oracle

Simer Plaha

Initial release

2016

2008

1980

2018

Current release

5.3.6, November 2023

23c, September 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

restricted free version is available

Open Source

GNU Affero GPL V3.0

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.

Implementation language

Java

C and C++

Scala

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

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

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

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

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

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

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Java
Kotlin
Scala

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

PL/SQL

also stored procedures in Java possible

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

yes

Replicated Map

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

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

ACID

isolation level can be parameterized

Atomic execution of operations

Concurrency

Support for concurrent manipulation of data

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

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

Planned for future releases

Role-based access control

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.