DBMS > Dgraph vs. Firebase Realtime Database vs. MySQL vs. Newts vs. PouchDB

System Properties Comparison Dgraph vs. Firebase Realtime Database vs. MySQL vs. Newts vs. PouchDB

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 open source RDBMS

Time Series DBMS based on Cassandra

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Graph DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Time Series DBMS

Document store

Secondary database models

Document store
Spatial DBMS

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

Score	1.53
Rank	#152	Overall
	#15	Graph DBMS

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	0.07
Rank	#375	Overall
	#41	Time Series DBMS

Score	2.34
Rank	#112	Overall
	#21	Document stores

Website

dgraph.io

firebase.google.com/products/realtime-database

www.mysql.com

opennms.github.io/newts

pouchdb.com

Technical documentation

dgraph.io/docs

firebase.google.com/docs/database

dev.mysql.com/doc

github.com/OpenNMS/newts/wiki

pouchdb.com/guides

Developer

Dgraph Labs, Inc.

Google

acquired by Google 2014

Oracle

since 2010, originally MySQL AB, then Sun

OpenNMS Group

Apache Software Foundation

Initial release

2016

2012

1995

2014

2012

Current release

8.4.0, April 2024

7.1.1, June 2019

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

Apache 2.0

Open Source

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

Java

JavaScript

Server operating systems

Linux
OS X
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

server-less, requires a JavaScript environment (browser, Node.js)

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

Secondary indexes

yes

via views

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

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

Android
iOS
JavaScript API
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
Java API

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

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

Java
JavaScript
Objective-C

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Java

JavaScript

Server-side scripts

Stored procedures

limited functionality with using 'rules'

yes

proprietary syntax

View functions in JavaScript

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

yes

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

based on Cassandra

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication
Source-replica replication

selectable replication factor

based on Cassandra

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

yes

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

Users with fine-grained authorization concept

no user groups or roles

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.