Google Cloud Essentials — selected guide
GCP vs. Firebase - Projects & storage
Eight concise orientations to compute, storage, containers, projects, delivery, logs, and errors
Eight 2020–2022 explainers introduce compute, storage, containers, Firebase projects, build tools, logging, and error reporting through the workloads each service supports.
Google Cloud Tech 5 of 8
In this collection Browse 8 summaries 5 of 8
Firebase and Google Cloud are not separate environments for the same app: a Firebase project is also a Google Cloud project. They share resources and billing, while Firebase adds tools aimed at mobile and web development. 00:00–01:03(opens in a new tab)
Key Points Covered
- The same project can appear in either console; deleting the Firebase project also deletes the underlying Google Cloud project and its resources. 01:03–02:07(opens in a new tab)
- Cloud Storage, Cloud Functions, and Cloud Firestore are shared products exposed through Firebase-specific SDKs and tooling. 02:07–03:12(opens in a new tab)
- Shared storage allows shared processing. In the presenter's example, a mobile app uploads pictures through Firebase, then a scheduled Google Cloud task resizes or crops those same pictures. 03:12–04:13(opens in a new tab)
- The access path still matters: Cloud Identity and Access Management (IAM) controls access to buckets and objects from Google Cloud services, while Firebase Security Rules control access through the Firebase client libraries. Sharing the data does not make these two permission systems interchangeable. 04:13–05:21(opens in a new tab)
Full video: https://www.youtube.com/watch?v=xbmYmgBEj4o(opens in a new tab)