DBMS > Firebase Realtime Database vs. Google Cloud Datastore vs. Snowflake vs. SpatiaLite

System Properties Comparison Firebase Realtime Database vs. Google Cloud Datastore vs. Snowflake vs. SpatiaLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

Spatial extension of SQLite

Primary database model

Document store

Relational DBMS

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

firebase.google.com/products/realtime-database

cloud.google.com/datastore

www.snowflake.com

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

firebase.google.com/docs/database

cloud.google.com/datastore/docs

docs.snowflake.net/manuals/index.html

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Google

acquired by Google 2014

Google

Snowflake Computing Inc.

Alessandro Furieri

Initial release

2012

2008

2014

2008

Current release

5.0.0, August 2020

License

Commercial or Open Source

commercial

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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

hosted

server-less

Data scheme

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language (GQL)

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

using Google App Engine

user defined functions

Triggers

Callbacks are triggered when data changes

Callbacks using the Google Apps Engine

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

yes

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

yes, based on authentication and database rules

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.