DBMS > Dgraph vs. Firebase Realtime Database vs. RocksDB vs. Yanza

System Properties Comparison Dgraph vs. Firebase Realtime Database vs. RocksDB vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

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.

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Time Series DBMS for IoT Applications

Primary database model

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	3.65
Rank	#85	Overall
	#11	Key-value stores

Website

dgraph.io

firebase.google.com/products/realtime-database

rocksdb.org

yanza.com

Technical documentation

dgraph.io/docs

firebase.google.com/docs/database

github.com/facebook/rocksdb/wiki

Developer

Dgraph Labs, Inc.

Google

acquired by Google 2014

Facebook, Inc.

Yanza

Initial release

2016

2012

2013

2015

Current release

8.11.4, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

BSD

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++

Server operating systems

Linux
OS X
Windows

hosted

Linux

Windows

Data scheme

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.

Secondary indexes

yes

SQL

Support of SQL

APIs and other access methods

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

Android
iOS
JavaScript API
RESTful HTTP API

C++ API
Java API

HTTP API

Supported programming languages

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

Java
JavaScript
Objective-C

C
C++
Go
Java
Perl
Python
Ruby

any language that supports HTTP calls

Server-side scripts

Stored procedures

limited functionality with using 'rules'

Triggers

Callbacks are triggered when data changes

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

yes

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Transaction concepts

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

ACID

yes

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

User concepts

Access control

Planned for future releases

yes, based on authentication and database rules

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.