DBMS > Dgraph vs. Firebase Realtime Database vs. Oracle vs. XTDB

System Properties Comparison Dgraph vs. Firebase Realtime Database vs. Oracle vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Distributed and scalable native Graph DBMS

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Widely used RDBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

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	14.29
Rank	#39	Overall
	#6	Document stores

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

dgraph.io

firebase.google.com/products/realtime-database

www.oracle.com/database

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

dgraph.io/docs

firebase.google.com/docs/database

docs.oracle.com/en/database

www.xtdb.com/docs

Developer

Dgraph Labs, Inc.

Google

acquired by Google 2014

Oracle

Juxt Ltd.

Initial release

2016

2012

1980

2019

Current release

23c, September 2023

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

MIT License

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C and C++

Clojure

Server operating systems

Linux
OS X
Windows

hosted

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

All OS with a Java 8 (and higher) VM
Linux

Data scheme

schema-free

yes

Schemaless in JSON and XML columns

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

limited SQL, making use of Apache Calcite

APIs and other access methods

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

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP REST
JDBC

Supported programming languages

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

Java
JavaScript
Objective-C

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

Clojure
Java

Server-side scripts

Stored procedures

limited functionality with using 'rules'

PL/SQL

also stored procedures in Java possible

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication
Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

ACID

isolation level can be parameterized

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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

yes, based on authentication and database rules

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.