Skip to content

Intermediate · Google Cloud and comparing the clouds · topic 28 of 50 · 30 min

Core Google Cloud services

Explanation

A dozen services cover most real projects on Google Cloud: Compute Engine for VMs, Cloud Storage for files, a global VPC and Cloud Load Balancing for networking, Cloud Run for containers that scale to zero, Cloud SQL and Firestore for databases, BigQuery for analytics, Pub/Sub for messaging and GKE for Kubernetes. Knowing what each one is for, and how it is billed, prevents most surprises.

A short tour

Google Cloud has well over a hundred services, but a small set covers most applications. This lesson explains what each core service does, when to use it, and the one or two billing facts that matter. If you know AWS or Azure already, the next lesson maps these services to their equivalents.

Compute Engine: virtual machines

Compute Engine gives you virtual machines (VMs) in any region. You pick a machine type, which sets the number of vCPUs (virtual processors) and the memory. Machine types come in families: general-purpose (for example the low-cost E2 series, good for web servers and small databases), compute-optimised (for heavy calculation), memory-optimised (for large in-memory databases) and accelerator-optimised (with GPUs for machine learning). An e2-medium, for example, has 2 shared vCPUs and 4 GB of memory.

Spot VMs are much cheaper, but Google can stop them at any time when it needs the capacity. They suit batch jobs that can restart. A managed instance group (MIG) runs many identical VMs from a template and can add or remove VMs automatically as load changes.

Cloud Storage: objects in buckets

Cloud Storage is object storage: you store files (objects) in buckets. Bucket names are globally unique. A bucket has a location (one region, a dual-region or a multi-region) and a default storage class. All classes have the same fast access and the same API. The difference is price: colder classes cost less per GB stored, but charge for reading data back and have a minimum storage duration. Delete an object early and you still pay for the minimum.

ClassMinimum storage durationGood for
StandardNoneData read often: website images, app uploads
Nearline30 daysData read about once a month or less: monthly reports
Coldline90 daysData read about once a quarter or less: older backups
Archive365 daysData read less than once a year: legal and audit archives
bash
gcloud storage buckets create gs://acme-invoices-2026 --location=asia-south1 --default-storage-class=STANDARD
gcloud storage cp invoice-1042.pdf gs://acme-invoices-2026/2026/10/
gcloud storage ls gs://acme-invoices-2026/2026/10/
Create a bucket in Mumbai, upload a file and list the folder.
Tip: Lifecycle rules can move objects to a colder class after a number of days, or delete them. Set one up on day one for logs and backups.

Networking: a global VPC and Cloud Load Balancing

A VPC (Virtual Private Cloud) is your private network in the cloud. In Google Cloud a VPC network is global, and its subnets are regional. One VPC can have a subnet in Mumbai and another in Delhi, and VMs in both talk over private IP addresses without any extra peering. This is different from AWS, where a VPC belongs to one region. Firewall rules are set on the VPC network.

Cloud Load Balancing spreads traffic across your backends. The global external Application Load Balancer gives you one public IP address that serves users worldwide and sends each request to the nearest healthy backend. Cloud CDN caches content close to users, and Cloud DNS hosts your domain names.

Serverless: Cloud Run, Cloud Run functions and App Engine

Cloud Run runs any container that listens for HTTP requests. You do not manage servers. It starts more copies (instances) when traffic grows and scales down to zero when nobody is calling, so a quiet service can cost almost nothing. Cloud Run jobs run containers that do a task and finish, such as a nightly report.

Cloud Run functions (called Cloud Functions until 2024) let you write just a function, for example in Python or Node.js. Google builds and runs the container for you. They suit small event handlers, such as resizing an image when it lands in a bucket. App Engine is Google's older platform for web apps. It is still supported, but many new projects choose Cloud Run.

bash
gcloud run deploy hello --source . --region asia-south1 --allow-unauthenticated
Builds the code in the current folder into a container and deploys it to Cloud Run in Mumbai, open to the public.

Databases

  • Cloud SQL: managed MySQL, PostgreSQL and SQL Server. Google handles backups, patches and failover. The default choice for a normal web app.
  • Firestore: a serverless NoSQL document database. It stores JSON-like documents and syncs well with mobile and web apps.
  • Spanner: a relational database that scales horizontally across regions with strong consistency. Powerful, and priced for large systems.

BigQuery: the serverless data warehouse

A data warehouse is a database built for analysis: big scans, totals and trends over millions or billions of rows. BigQuery is serverless, so you write SQL and Google finds the machines. Storage and compute are billed separately. For compute you choose on-demand pricing, where you pay per TiB (tebibyte, 1024 to the power 4 bytes) of data your queries scan, with a monthly free amount, or capacity pricing, where you reserve processing power (slots) for a steady price.

BigQuery stores data by column. A query that selects 3 columns reads only those 3 columns, so SELECT * on a wide table costs far more than naming the columns you need. Adding LIMIT 10 does not reduce the data scanned on a normal table. Partitioning a table by date lets a query that filters on date read only the matching days.

bash
bq query --use_legacy_sql=false --dry_run 'SELECT city, SUM(amount) FROM shop.orders WHERE order_date = "2026-10-01" GROUP BY city'
A dry run reports how many bytes the query would process, without running it or charging for it.

Pub/Sub and GKE

Pub/Sub is a messaging service. Publishers send messages to a topic, and each subscription delivers them to a subscriber. It decouples parts of a system: the order service publishes "order placed" and the email, invoice and analytics services each react in their own time. GKE (Google Kubernetes Engine) runs Kubernetes for you in Standard or Autopilot mode; module 8 covers it.

Free tier

Google Cloud has a Free Program with two parts: trial credit for new customers to spend in the first months, and an always-free tier with monthly limits on some products (for example a small e2-micro VM in certain US regions and a monthly amount of BigQuery queries). The amounts and rules change, so check the current Google Cloud Free Program page before relying on them.

Careful: Common mistakes: leaving test VMs running all month (stop or delete them, and set a budget); putting often-read data in Archive (retrieval fees and the 365-day minimum make it expensive); running SELECT * on huge BigQuery tables (name your columns and dry-run first); making a bucket public by accident (keep public access prevention on); and choosing a US region for Indian users' data (pick asia-south1 or asia-south2 for latency and data-residency rules).

Need help?

Stuck on a word or an idea? Search this course, or every course, and jump straight to the explanation or a worked question.

Try:

Watch the lesson

Core Google Cloud services · 1/8

Core Google Cloud services

This lesson tours the Google Cloud services you will use most, and the billing facts that matter.

Prefer a video by a teacher? Find free videos on “google cloud core services overview cloud run bigquery cloud storage” on YouTube ↗

In real life: A food delivery startup in Hyderabad

A food delivery startup in Hyderabad runs its order API on Cloud Run in asia-south1 and its main database on Cloud SQL for PostgreSQL. Restaurant photos sit in a Standard Cloud Storage bucket behind Cloud CDN, and old invoices move to Coldline after 90 days through a lifecycle rule. Each order is published to Pub/Sub, and a subscriber streams it into BigQuery. On Monday mornings, the business team runs SQL in BigQuery to see orders by area and hour. After an analyst ran SELECT * on the full orders table every hour, the team partitioned the table by date and set a budget alert. Their BigQuery bill fell sharply.

Practice (0/3 done)

Task 1 · Code · Python

Write storage_class(days_between_reads) that suggests a Cloud Storage class using this simple rule: fewer than 30 days between reads gives "STANDARD", 30 to 89 days gives "NEARLINE", 90 to 364 days gives "COLDLINE", and 365 days or more gives "ARCHIVE".

Task 2 · Code · Python

Write bigquery_cost(bytes_scanned, price_per_tib, free_tib) that estimates a month's BigQuery on-demand query cost. bytes_scanned is a list with the bytes each query scanned. 1 TiB is 1024 ** 4 bytes. Add up all the bytes, convert to TiB, subtract the free TiB for the month (never going below zero), multiply by price_per_tib and round to 2 decimal places. The rates are passed in because real prices differ by region and change over time.

Task 3 · Question

A BigQuery table has 60 columns and 2 TB of data. Which query scans the LEAST data?

Quick quiz

Question 1

1.What is the minimum storage duration of the Coldline storage class?

Question 2

2.How is a VPC network scoped in Google Cloud?

Question 3

3.Which service runs your container, scales with traffic and can scale down to zero?

Question 4

4.What were Cloud Run functions called before 2024?

Question 5

5.With BigQuery on-demand pricing, what are queries charged by?

Read more (free)

Open a question to see the answer and why. The first ones are this topic's own quiz, so try the quiz above before you peek.

What is the minimum storage duration of the Coldline storage class?

Answer: 90 days

Coldline has a 90-day minimum. Nearline is 30 days and Archive is 365 days.

How is a VPC network scoped in Google Cloud?

Answer: Global, with regional subnets

Google Cloud VPC networks are global resources; each subnet lives in one region.

Which service runs your container, scales with traffic and can scale down to zero?

Answer: Cloud Run

Cloud Run is serverless containers with scale to zero.

What were Cloud Run functions called before 2024?

Answer: Cloud Functions

Google renamed Cloud Functions to Cloud Run functions in 2024.

With BigQuery on-demand pricing, what are queries charged by?

Answer: The bytes of data scanned

On-demand compute is charged per TiB scanned, with a monthly free amount. Storage is billed separately.

What is the closest Google Cloud equivalent of AWS Lambda?Related

Answer: Cloud Run functions

Cloud Run functions (formerly Cloud Functions) run single functions on events, like Lambda.

From AWS vs Azure vs Google Cloud: the service map

A team moves an app from Cloud Run to GKE. What usually stays the same?Related

Answer: The container image

The image is portable; the configuration around it changes.

From Choosing where to run a container

What protects VMs against a whole datacentre in a region going down?Related

Answer: Spreading them across availability zones

Zones are physically separate datacentres. An availability set only spreads VMs across racks in one datacentre.

From Azure compute and storage

How is data organised in Cloud Firestore?Related

Answer: Collections of documents

Firestore is a document database.

From Firebase basics

Pass the quiz (60% or more) or mark this topic as done when you are ready.

Your progress is saved on this device only.

Next steps

  1. 2 more topics in “Google Cloud and comparing the clouds” before its exam: AWS vs Azure vs Google Cloud: the service map, The command line on all three clouds.
  2. Module 7 exam: Google Cloud and comparing the clouds · 12 questions · 20 min, without help. 4 topics of this module still to finish first.
  3. Then the next module, Containers in the cloud. 50 topics left in the course before the final exam.

← Previous: Google Cloud structure: projects, billing and IAM