Introduction to GCP
Google Cloud Platform (GCP) is Google’s suite of cloud computing services running on the same infrastructure that powers Google Search, YouTube, and Gmail. GCP emphasizes data analytics, machine learning, Kubernetes, and open-source technologies. Understanding GCP’s design philosophy — global networking, per-second billing, and project-based isolation — helps you make better architectural decisions from day one.
What Is GCP?
GCP provides IaaS, PaaS, and SaaS through a global network of regions and zones. Distinctive characteristics include:
- Global network: Google’s private fiber network delivers low-latency connectivity between regions
- Kubernetes leadership: GKE is the reference Kubernetes implementation; Google invented Kubernetes
- Data and AI: BigQuery, Vertex AI, and TensorFlow integration for analytics and ML pipelines
- Sustained use discounts: Automatic discounts for long-running Compute Engine workloads
- Per-second billing: Many services bill by the second, not the hour — cost savings for bursty workloads
Global Infrastructure
Region (e.g., us-central1)
├── Zone a (us-central1-a) — independent failure domain
├── Zone b (us-central1-b) — independent failure domain
└── Zone c (us-central1-c) — independent failure domain
| Concept | Description | Example |
|---|---|---|
| Region | Geographic area with low-latency zones | us-central1, europe-west1 |
| Zone | Isolated datacenter within a region | us-central1-a |
| Multi-region | Services replicated across regions | Cloud Storage multi-region buckets |
| Global | Single logical endpoint worldwide | Cloud Load Balancing, Cloud CDN |
Deploy production workloads across at least two zones in a region for zone-level fault tolerance.
Core Service Categories
| Category | Key Services | Typical Use |
|---|---|---|
| Compute | Compute Engine, GKE, Cloud Run, Cloud Functions | Hosting applications |
| Storage | Cloud Storage, Persistent Disk, Filestore | Data persistence |
| Databases | Cloud SQL, Firestore, BigQuery, Spanner | Managed data services |
| Networking | VPC, Cloud Load Balancing, Cloud CDN, Cloud NAT | Connectivity and delivery |
| Identity | IAM, Workload Identity, Organization policies | Access control |
| DevOps | Cloud Build, Artifact Registry, Cloud Deploy | CI/CD pipelines |
| AI/ML | Vertex AI, AutoML, Vision API | Model training and inference |
GCP vs. Other Clouds
| Dimension | GCP | AWS | Azure |
|---|---|---|---|
| Market share | #3 globally | #1 | #2 |
| Kubernetes | GKE (originator) | EKS | AKS |
| Data analytics | BigQuery (serverless, petabyte-scale) | Redshift, Athena | Synapse |
| Pricing model | Per-second, sustained use discounts | Per-hour (many services) | Per-minute/hour |
| Enterprise integration | Strong open-source, less Microsoft-centric | Broadest service catalog | Deep Microsoft 365/AD |
| Network | Global VPC, private backbone | Regional VPCs | Regional VNets |
GCP excels in data analytics (BigQuery), machine learning (Vertex AI), and Kubernetes (GKE). Organizations with strong open-source and container cultures often prefer GCP. AWS leads in breadth; Azure leads in enterprise Microsoft integration.
Pricing Model
GCP uses pay-as-you-go pricing with sustained use discounts applied automatically. Committed use discounts (1 or 3 years) offer additional savings for predictable workloads.
| Pricing Feature | How It Works |
|---|---|
| Free tier | Always-free quotas for Compute Engine, Cloud Storage, BigQuery, etc. |
| Free trial | $300 credit for 90 days on new accounts |
| Sustained use | Automatic discount up to 30% for VMs running >25% of the month |
| Committed use (CUD) | 1- or 3-year commitment for up to 57% discount |
| Preemptible/Spot VMs | Up to 91% discount for interruptible workloads |
Use the GCP Pricing Calculator to estimate costs before deployment.
Real-World Scenarios
| Scenario | Recommended GCP Services |
|---|---|
| Startup web app | Cloud Run + Cloud SQL + Cloud Storage |
| Data warehouse | BigQuery + Cloud Storage + Dataflow |
| ML pipeline | Vertex AI + GKE + Cloud Storage |
| Enterprise migration | Compute Engine + Migrate to VMs + Cloud SQL |
| Event-driven microservices | Pub/Sub + Cloud Functions + Firestore |
Getting Started
- Create an account at cloud.google.com/free
- Create a project in the Google Cloud Console
- Install the Google Cloud CLI:
# macOS
brew install google-cloud-sdk
# Verify and authenticate
gcloud --version
gcloud auth login
gcloud config set project my-learning-project
- Enable APIs as needed:
gcloud services enable compute.googleapis.com storage.googleapis.com \
sqladmin.googleapis.com container.googleapis.com
- Verify your setup:
gcloud projects describe my-learning-project
gcloud compute regions list
Common Mistakes
| Mistake | Why It Hurts | Fix |
|---|---|---|
| Using default project | Resources scattered, billing unclear | Create named projects per environment |
| Ignoring free tier limits | Unexpected charges after quota | Review free tier quotas |
| Choosing wrong region | Latency, compliance issues | Pick region closest to users; check data residency |
| No billing alerts | Cost surprises | Set budgets in first week |
| Using personal Gmail for prod | No enterprise controls | Use Google Workspace or Cloud Identity |
Best Practices
- One project per environment (dev, staging, prod) for billing isolation
- Enable APIs only when needed to reduce attack surface
- Use folders and organizations as your GCP footprint grows
- Label everything from day one for cost allocation
- Start with managed services (Cloud SQL, Cloud Run) before self-managing VMs
Troubleshooting
“Permission denied” on first API call:
gcloud auth list # Verify active account
gcloud projects get-iam-policy my-learning-project # Check your roles
“API not enabled” error:
gcloud services enable SERVICE_NAME.googleapis.com
gcloud services list --enabled # Confirm activation
Billing not linked:
gcloud billing accounts list
gcloud billing projects link my-learning-project --billing-account=ACCOUNT_ID
Understanding GCP’s project-based structure and global infrastructure sets the foundation for the rest of this learning path.
Next: GCP Account Setup — projects, billing, and local tooling.