DBMS > Dgraph vs. Oracle vs. OrientDB vs. SiteWhere

System Properties Comparison Dgraph vs. Oracle vs. OrientDB vs. SiteWhere

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 RDBMS

Multi-model DBMS (Document, Graph, Key/Value)

M2M integration platform for persisting/querying time series data

Primary database model

Graph DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store

Time Series DBMS

Secondary database models

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	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

dgraph.io

www.oracle.com/database

orientdb.org

github.com/sitewhere/sitewhere

Technical documentation

dgraph.io/docs

docs.oracle.com/en/database

www.orientdb.com/docs/last/index.html

sitewhere1.sitewhere.io/index.html

Developer

Dgraph Labs, Inc.

Oracle

OrientDB LTD; CallidusCloud; SAP

SiteWhere

Initial release

2016

1980

2010

Current release

23c, September 2023

3.2.29, March 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

Apache version 2

Open Source

Common Public Attribution License Version 1.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

C and C++

Java

Server operating systems

Linux
OS X
Windows

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

All OS with a Java JDK (>= JDK 6)

Linux
OS X
Windows

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

predefined scheme

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

SQL-like query language, no joins

APIs and other access methods

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

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

HTTP REST

Supported programming languages

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

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

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

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

Java, Javascript

Triggers

yes

Hooks

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding, horizontal partitioning

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication
Source-replica replication

Multi-source replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

Transaction concepts

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

ACID

isolation level can be parameterized

ACID

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'

User concepts

Access control

Planned for future releases

fine grained access rights according to SQL-standard

Access rights for users and roles; record level security configurable

Users with fine-grained authorization concept

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.