03 - The 4 Ways to Interact with GCP

Welcome to Day 03 of Learn GCP in 30 Days! Today, we answer a fundamental developer question: How do developers actually build and control things on Google Cloud?

One Task, Four Different Ways

To understand why 4 different methods exist, imagine a simple task: You want to create a new Virtual Server (VM) named my-web-server on GCP.

Here is how a developer accomplishes that exact same task using each of the 4 methods:

Notice that all 4 methods achieve the exact same end result—creating a server in Google's data center—but each method is built for a different developer scenario!

Detailed Breakdown of the 4 Methods

Method 1: GCP Web Console (Visual Button Clicks)

Developer Experience: "I want to visually explore GCP and click buttons in my web browser."

• How it Works: You log into console.cloud.google.com on your browser and use your mouse to click buttons, fill out web forms, and view visual charts.
• Best For:
  • Absolute beginners exploring GCP for the first time.
  • One-time visual checks (e.g., checking billing charts or reading error logs).
  • Quick visual debugging.
• The Drawback: Slow and prone to human misclicks. If you need to create 50 identical servers, clicking buttons 50 times in a web browser takes hours and leads to mistakes.

Method 2: gcloud CLI & Cloud Shell (Terminal Commands)

Developer Experience: "Skip the web browser clicks! Give me 1 fast command to create or delete a service."

• How it Works: You open Cloud Shell (or your laptop terminal) and type single-line gcloud commands.
• Example Command:
  bash

  gcloud compute instances create my-web-server --zone=asia-south1-a
  

• Best For:
  • Fast developer tasks without waiting for web pages to load.
  • Quick bash scripts that automate repetitive tasks.
• Key Difference: gcloud is the command tool, while Cloud Shell is the free web browser terminal where gcloud is pre-installed.

Method 3: Client SDK Libraries (Writing Code Inside Your App)

Developer Experience: "My application code needs to automatically talk to GCP without any human intervention."

• How it Works: You install Google's official software library inside your programming language (Python, Node.js, Java, Go) so your application code can upload files or save database records automatically.
• Real-World Example: When a user registers on your mobile app and uploads a profile picture, your Node.js code automatically sends that picture to Cloud Storage using 3 lines of code:
  javascript

  // Node.js Code inside your backend app
  const { Storage } = require('@google-cloud/storage');
  const storage = new Storage();
  await storage.bucket('my-user-avatars').upload('profile.jpg');
  

• Best For: Connecting your application's backend code directly to GCP storage, databases, and AI models.

Method 4: Infrastructure as Code / Terraform (Automated Infrastructure Files)

Developer Experience: "Write my entire cloud setup inside a text file so I can create or recreate 100 servers in 1 click."

• How it Works: Instead of clicking web buttons or typing individual commands, developers write a text configuration file (using a tool called Terraform or GCP Deployment Manager) that describes their entire cloud architecture.
• Example Blueprint File (main.tf):
  hcl

  resource "google_compute_instance" "web" {
    name         = "production-server"
    machine_type = "e2-medium"
    zone         = "asia-south1-a"
  }
  

• Why Professional Companies Use It:
  • Zero Human Error: No risk of a developer forgetting to check a security box in a web form.
  • Instant Disaster Recovery: If an entire cloud environment is deleted, running terraform apply recreates 100 servers, databases, and firewalls in 2 minutes automatically!
  • Version Control: Infrastructure changes can be tracked in Git just like regular code.

Signal vs. Noise: What to Remember vs. What to Ignore

Common Doubts & Interview Traps

Q1: Why don't professional tech companies use the Web Console button clicks for their production systems?

• Answer: Manual UI button clicks introduce human error! A developer might accidentally select the wrong firewall setting or forget a security parameter. Professional companies use Terraform (IaC) so every resource configuration is reviewed, tested, and tracked in code repositories (Git).

Q2: Is Cloud Shell the same thing as the gcloud CLI?

• Answer: No, they are two different things working together:
  • gcloud CLI: This is the software command program (like Git or Python) that runs commands to control GCP. You can install gcloud on your personal Windows laptop or Mac.
  • Cloud Shell: This is the built-in terminal window directly inside your GCP account. Google created Cloud Shell so you don't have to install anything on your personal laptop—it gives you a terminal inside your browser with gcloud pre-installed and pre-logged into your GCP account!

Daily Practice Drill & Self-Check

Test your understanding of today's lesson:

// Try answering these:
1. You are building a Python backend for an online food delivery app. When a customer places an order, your Python code needs to save the order details to a GCP database automatically. Which of the 4 interaction methods should your Python code use?
2. A company wants to make sure their entire cloud server setup can be rebuilt automatically in 2 minutes if a disaster occurs. Which method allows them to define their entire cloud setup as code?

🎉 Awesome job! You have completed Day 03.

You now understand the 4 ways developers control Google Cloud, from visual UI clicks to automated Terraform blueprints. Take a break, let today's concepts sink in, and come back tomorrow fresh!

Tomorrow on Day 04, we will explore GCP Resource Hierarchy (Organizations, Folders, and Projects) so you understand how companies organize and structure their cloud projects safely.

← 02 - Navigating the GCP Console Website | Next Topic → 04 - Resource Hierarchy - Org, Folders, Projects