Skip to main content
Cloud Computing

Google Cloud Tutorial with Examples.

Google Cloud tutorial with examples: GKE, BigQuery, Cloud Run, Cloud Storage, Pub/Sub and core GCP architecture patterns.

Architecture at a glance

Click any box to open the lesson that teaches it

GCP architecture at a glance

gcloud → IAM → VPC → Compute Engine / Cloud Run & Functions → Storage / SQL, watched by Monitoring

GCP architecture at a glance A gcloud call runs as an identity restricted by an IAM role, inside a project. Compute lives inside a VPC's subnets and firewall rules: Compute Engine for servers you manage, Cloud Run and Cloud Functions for serverless code. Both call Cloud Storage for object storage and Cloud SQL for a managed database. Terraform provisions the whole stack as one config and Cloud Monitoring watches it with metrics and log-based alerting, with Cost and Billing and the Architecture Framework's five pillars as the final check. gcloud CLI projectgcloud init IAM rolesaccounts VPC subnetfirewall Compute Engine VM · SSH Cloud Run & Functionsserverless Data Cloud Storage buckets · objects Cloud SQL Postgres · Auth Proxy Deploys & watches Terraform config · apply Cloud Monitoring metrics · alerting Cost & reliability Cost & Billing billing export · Architecture Framework
How it fits together (5 steps)
  1. Every call starts from gcloud, initialized and confirmed against the right project before anything runs — every VM, bucket, and database belongs to exactly one project.
  2. That call only works as far as its IAM role allows: a service account with no binding gets a real PERMISSION_DENIED until a role is granted — a permission is one fine-grained action, a role is a named bundle of them.
  3. Compute lives inside a VPC, where a firewall rule has to allow a port before anything reaches a subnet, independently of whether the instance has a public IP. Compute Engine runs a VM you SSH into once port 22 is open; Cloud Run and Cloud Functions run the same kind of code with no server to manage, at the cost of a cold start that can be an order of magnitude slower than a warm request.
  4. Both call the data layer: Cloud Storage holds objects in a bucket across Standard, Nearline, Coldline and Archive classes, and Cloud SQL runs a managed Postgres instance reached through the Auth Proxy's encrypted tunnel, without allow-listing an IP.
  5. Two services wrap the whole stack: Terraform applies a config as one plan-then-apply step, tracked in a state file, and Cloud Monitoring collects the metrics and log-based alerting that watch it while it runs. Cost and Billing, checked against the Architecture Framework's five pillars, is the last step before calling it production-ready.

Beginner

Start here — no prior experience needed

4 lessons

Intermediate

For developers with core concepts down

5 lessons

Advanced

Production-grade patterns for experienced engineers

1 lesson