DBMS > Dgraph vs. Google Cloud Firestore vs. GridGain vs. Snowflake

System Properties Comparison Dgraph vs. Google Cloud Firestore vs. GridGain vs. Snowflake

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 Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

GridGain is an in-memory computing platform, built on Apache Ignite

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Graph DBMS

Document store

Key-value store
Relational DBMS

Relational DBMS

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

Score	1.48
Rank	#158	Overall
	#15	Graph DBMS

Score	8.96
Rank	#48	Overall
	#8	Document stores

Score	1.53
Rank	#155	Overall
	#26	Key-value stores
	#73	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

dgraph.io

firebase.google.com/products/firestore

www.gridgain.com

www.snowflake.com

Technical documentation

dgraph.io/docs

firebase.google.com/docs/firestore

www.gridgain.com/docs/index.html

docs.snowflake.net/manuals/index.html

Developer

Dgraph Labs, Inc.

Google

GridGain Systems, Inc.

Snowflake Computing Inc.

Initial release

2016

2017

2007

2014

Current release

GridGain 8.5.1

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

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

Java, C++, .Net

Server operating systems

Linux
OS X
Windows

hosted

Linux
OS X
Solaris
Windows

hosted

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

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

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

CLI Client
JDBC
ODBC

Supported programming languages

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

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

yes (compute grid and cache interceptors can be used instead)

user defined functions

Triggers

yes, with Cloud Functions

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication via Raft

Multi-source replication

yes (replicated cache)

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

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

User concepts

Access control

Planned for future releases

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

Security Hooks for custom implementations

Users with fine-grained authorization concept, user roles and pluggable authentication

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.