DBMS > Firebase Realtime Database vs. Google Cloud Datastore
System Properties Comparison Firebase Realtime Database vs. Google Cloud Datastore
Please select another system to include it in the comparison.
|Editorial information provided by DB-Engines
|Firebase Realtime Database Xexclude from comparison
|Google Cloud Datastore Xexclude from comparison
|Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform
|Primary database model
|Google acquired by Google 2014
|License Commercial or Open Source
|Cloud-based only Only available as a cloud service
|DBaaS offerings (sponsored links) Database as a Service
Providers of DBaaS offerings, please contact us to be listed.
|Server operating systems
|Typing predefined data types such as float or date
|yes, details here
|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.
|SQL Support of SQL
|SQL-like query language (GQL)
|APIs and other access methods
RESTful HTTP API
|gRPC (using protocol buffers) API
RESTful HTTP/JSON API
|Supported programming languages
|Server-side scripts Stored procedures
|limited functionality with using 'rules'
|using Google App Engine
|Callbacks are triggered when data changes
|Callbacks using the Google Apps Engine
|Partitioning methods Methods for storing different data on different nodes
|Replication methods Methods for redundantly storing data on multiple nodes
|Multi-source replication using Paxos
|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.
|Foreign keys Referential integrity
|yes via ReferenceProperties or Ancestor paths
|Transaction concepts Support to ensure data integrity after non-atomic manipulations of data
|ACID Serializable Isolation within Transactions, Read Committed outside of Transactions
|Concurrency Support for concurrent manipulation of data
|Durability Support for making data persistent
|In-memory capabilities Is there an option to define some or all structures to be held in-memory only.
|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)
More information provided by the system vendor
We invite representatives of system vendors to contact us for updating and extending the system information,
Related products and services
We invite representatives of vendors of related products to contact us for presenting information about their offerings here.
|Firebase Realtime Database
|Google Cloud Datastore
|DB-Engines blog posts
|Recent citations in the news
Atos cybersecurity blog: Misconfigured Firebase: A real-time cyber threat
Realtime vs Cloud Firestore: Which Firebase Database to go?
Firebase Played Us!
Clash of Clans gamers at risk while using third-party app
How to use Firebase to develop cloud-based multiplayer mobile games
provided by Google News
Google says it'll stop charging fees to transfer data out of Google Cloud
NetApp Cloud Volumes Service datastore support for Google Cloud VMware Engine
3 Useful tips for using Google Cloud Datastore.
Google’s Cloud Platform Gets Improved Hadoop Support With BigQuery And Cloud Datastore Connectors
Google wants your WordPress blog—and everything else—in its cloud
provided by Google News
Share this page