Google Cloud
Google Cloud Platform (GCP): Cloud Storage, Cloud Run and Identity Platform as managed services instead of a server.
Cloud & DevOpsUsing since 2022 · Featured project: CAS Marketplace (in the Code & Pepper team)
- Category
- Cloud & DevOps
- Using since
- 2022
- Featured project
- CAS Marketplacein the Code & Pepper team
In practice
I pick Google Cloud when the company already works in it or the app should rest on ready services such as storage and sign-in. GCP is in the stack of Gaia Lens and CAS Marketplace, both done in the Code & Pepper team. I never swap a single server for a cloud by force.
What is Google Cloud?
Google Cloud, GCP for short, is the cloud of Google, where managed services stand in for servers of your own. Cloud Storage is object storage, with data in buckets. Cloud Run is a managed platform for running containers and functions, with no cluster to create. Identity Platform supplies services and SDKs for signing users in.
Infrastructure configuration can live in plain files. Infrastructure Manager is a Google service that deploys Terraform configurations and shows a preview before a change. For mobile apps Google also has a separate platform, Firebase.
- Kind
- The Google cloud, managed services
- Files
- Cloud Storage, an object store
- Code without servers
- Cloud Run, a platform for containers and functions
- Sign-in
- Identity Platform, services and SDKs
How I work with Google Cloud
I start by asking where the project already stands: who holds the Google Cloud account and what runs in it. Only then do I choose services, and only those that take server upkeep off my plate.
Services matched to the job
Files go to Cloud Storage, code without a server of its own to Cloud Run, and sign-in I leave to a ready service instead of writing it from scratch. On Gaia Lens GCP is a scalable cloud where AI models run.
Infrastructure in the repository
I describe resources in code, so a change goes through review. On Google Cloud I do it with Terraform, and Infrastructure Manager deploys that configuration. Before a change I look at the preview, not just the result.
Account and roles
The Google Cloud project and the bill belong to the company, not to me. I get the roles the work needs and nothing more, and when the work ends I hand the access back.
When it fits, and when it doesn't
Google Cloud fits where a project already sits near Google services or can lean on managed parts instead of a server somebody has to run.
A good fit when
- A project that already runs on Google Cloud or belongs to a company that keeps its data there.
- A containerised app that nobody should have to run on a server, in Cloud Run for example.
- User uploads kept apart from the app, in Cloud Storage.
Not a fit when
- A brochure site that runs happily on ordinary hosting.
- A single app on a VPS of your own, in a Docker container.
- A team with nobody to handle cloud permissions and billing.
When a project already stands on Amazon, I stay with AWS, and the comparison of the two clouds is in that entry. For a mobile app with sign-in and a database I check Firebase first, the Google platform.
Frequently asked questions
A project meant for Google Cloud?
Write where the project runs today, who holds the cloud account and what the app has to store. I will answer whether Google Cloud fits, or whether another provider or a plain server is better.