DBMS > Dgraph vs. Firebase Realtime Database vs. Microsoft Azure Cosmos DB vs. Typesense

System Properties Comparison Dgraph vs. Firebase Realtime Database vs. Microsoft Azure Cosmos DB vs. Typesense

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.

Globally distributed, horizontally scalable, multi-model database service

A typo-tolerant, in-memory search engine optimized for instant search-as-you-type experiences and developer productivity

Primary database model

Graph DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Search engine

Secondary database models

Spatial DBMS

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	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	0.79
Rank	#210	Overall
	#14	Search engines

Website

dgraph.io

firebase.google.com/products/realtime-database

azure.microsoft.com/services/cosmos-db

typesense.org

Technical documentation

dgraph.io/docs

firebase.google.com/docs/database

learn.microsoft.com/azure/cosmos-db

typesense.org/docs

Developer

Dgraph Labs, Inc.

Google

acquired by Google 2014

Microsoft

Initial release

2016

2012

2014

2015

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

GPL V3

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++

Server operating systems

Linux
OS X
Windows

hosted

Linux

Data scheme

schema-free

pre-defined schema optional

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

SQL-like query language

APIs and other access methods

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

Android
iOS
JavaScript API
RESTful HTTP API

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

RESTful HTTP API

Supported programming languages

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

Java
JavaScript
Objective-C

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

.Net

community maintained
Clojure

community maintained
Dart

community maintained
Go

community maintained
Java

community maintained
JavaScript
Perl

community maintained
PHP
Python
Ruby
Rust

community maintained
Swift

community maintained

Server-side scripts

Stored procedures

limited functionality with using 'rules'

JavaScript

Triggers

Callbacks are triggered when data changes

JavaScript

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

yes

Implicit feature of the cloud service

Multi-source replication using RAFT

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

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

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

yes

Multi-item ACID transactions with snapshot isolation within a partition

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

Access rights can be defined down to the item level

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.