Gcp Cloud Architect
Pick the right Google Cloud architecture pattern (serverless web, GKE microservices, data pipeline, ML, multi-region HA) with cost and complexity tradeoffs before you provision GCP.
Overview
GCP Cloud Architect is an agent skill most often used in Build (also Validate scope, Operate infra) that matches application requirements to six Google Cloud architecture patterns with cost and complexity guidance.
Install
npx skills add https://github.com/alirezarezvani/claude-skills --skill gcp-cloud-architectWhat is this skill?
- Pattern selection matrix across 6 architectures with user scale, monthly cost bands, and complexity ratings
- Serverless web pattern for MVP/SaaS/mobile backends under ~50K users ($30–400/mo)
- Microservices on GKE and three-tier patterns for 10K–500K traffic tiers
- Serverless data pipeline and ML platform patterns with medium-to-high complexity guidance
- Multi-region high-availability pattern for global apps and disaster recovery
- 6 architecture patterns with selection matrix
- Serverless web indicative range $30–400/month for under 50K users
- Microservices on GKE indicative range $400–2500/month for 10K–500K users
Adoption & trust: 559 installs on skills.sh; 17.5k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know you want to run on GCP but cannot tell whether serverless, GKE, a three-tier stack, or a pipeline/ML layout fits your traffic, budget, and team size.
Who is it for?
Solo builders scoping an MVP, SaaS API, or data/ML workload on GCP who need a pattern pick before writing infra code.
Skip if: Teams that already have a locked enterprise reference architecture, or builders who only need a single-service tutorial without cross-pattern comparison.
When should I use this skill?
Selecting GCP architecture before provisioning or when comparing serverless, GKE, tiered, pipeline, ML, or HA layouts.
What do I get? / Deliverables
You leave with a named pattern, scale/cost band, and structural diagram direction so provisioning and implementation plans target the right GCP services.
- Recommended pattern from the 6-pattern catalog
- Cost/complexity band aligned to the selection matrix
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Architecture pattern choice is the canonical backend/infra decision most solo builders make during initial GCP build-out. The skill maps workloads to Cloud Run, GKE, three-tier, pipelines, and ML stacks—core backend and platform design on GCP.
Where it fits
Compare serverless web vs three-tier cost bands before committing build budget on GCP.
Choose Pattern 1 serverless web for a mobile backend under 50K users.
Pick the serverless data pipeline pattern for analytics ETL without managing clusters.
Evaluate multi-region HA when traffic crosses 100K and disaster recovery becomes mandatory.
How it compares
Architecture pattern reference for GCP—not a Terraform generator or a security audit skill.
Common Questions / FAQ
Who is gcp-cloud-architect for?
Indie developers and small teams choosing how to structure apps on Google Cloud before they commit to Cloud Run, GKE, or classic tiered stacks.
When should I use gcp-cloud-architect?
During Validate when sizing scope and cost, during Build when designing backend/infra, and during Operate when planning multi-region HA or pipeline upgrades.
Is gcp-cloud-architect safe to install?
It is reference documentation without built-in shell or cloud mutations; review the Security Audits panel on this Prism page before installing any skill package.
SKILL.md
READMESKILL.md - Gcp Cloud Architect
# GCP Architecture Patterns Reference guide for selecting the right GCP architecture pattern based on application requirements. --- ## Table of Contents - [Pattern Selection Matrix](#pattern-selection-matrix) - [Pattern 1: Serverless Web Application](#pattern-1-serverless-web-application) - [Pattern 2: Microservices on GKE](#pattern-2-microservices-on-gke) - [Pattern 3: Three-Tier Application](#pattern-3-three-tier-application) - [Pattern 4: Serverless Data Pipeline](#pattern-4-serverless-data-pipeline) - [Pattern 5: ML Platform](#pattern-5-ml-platform) - [Pattern 6: Multi-Region High Availability](#pattern-6-multi-region-high-availability) --- ## Pattern Selection Matrix | Pattern | Best For | Users | Monthly Cost | Complexity | |---------|----------|-------|--------------|------------| | Serverless Web | MVP, SaaS, mobile backend | <50K | $30-400 | Low | | Microservices on GKE | Complex services, enterprise | 10K-500K | $400-2500 | Medium | | Three-Tier | Traditional web, e-commerce | 10K-200K | $300-1500 | Medium | | Data Pipeline | Analytics, ETL, streaming | Any | $100-2000 | Medium-High | | ML Platform | Training, serving, MLOps | Any | $200-5000 | High | | Multi-Region HA | Global apps, DR | >100K | 2x single | High | --- ## Pattern 1: Serverless Web Application ### Use Case SaaS platforms, mobile backends, low-traffic websites, MVPs ### Architecture Diagram ``` ┌─────────────┐ ┌─────────────┐ ┌─────────────┐ │ Cloud CDN │────▶│ Cloud │ │ Identity │ │ (CDN) │ │ Storage │ │ Platform │ └─────────────┘ │ (Static) │ │ (Auth) │ └─────────────┘ └──────┬──────┘ │ ┌─────────────┐ ┌─────────────┐ ┌──────▼──────┐ │ Cloud DNS │────▶│ Cloud │────▶│ Cloud Run │ │ (DNS) │ │ Load Bal. │ │ (API) │ └─────────────┘ └─────────────┘ └──────┬──────┘ │ ┌──────▼──────┐ │ Firestore │ │ (Database) │ └─────────────┘ ``` ### Service Stack | Layer | Service | Configuration | |-------|---------|---------------| | Frontend | Cloud Storage + Cloud CDN | Static hosting with HTTPS | | API | Cloud Run | Containerized API with auto-scaling | | Database | Firestore | Native mode, pay-per-operation | | Auth | Identity Platform | Multi-provider authentication | | CI/CD | Cloud Build | Automated container deployments | ### Terraform Example ```hcl resource "google_cloud_run_v2_service" "api" { name = "my-app-api" location = "us-central1" template { containers { image = "gcr.io/my-project/my-app:latest" resources { limits = { cpu = "1000m" memory = "512Mi" } } } scaling { min_instance_count = 0 max_instance_count = 10 } } } ``` ### Cost Breakdown (10K users) | Service | Monthly Cost | |---------|-------------| | Cloud Run | $5-25 | | Firestore | $5-30 | | Cloud CDN | $5-15 | | Cloud Storage | $1-5 | | Identity Platform | $0-10 | | **Total** | **$16-85** | ### Pros and Cons **Pros:** - Scale-to-zero (pay nothing when idle) - Container-based (no runtime restrictions) - Built-in HTTPS and custom domains - Auto-scaling with no configuration **Cons:** - Cold starts if min instances = 0 - Firestore query limitations vs SQL - Vendor lock-in to GCP --- ## Pattern 2: Microservices on GKE ### Use Case Complex business systems, enterprise applications, platform engineering ### Architecture Diagram ``` ┌─────────────┐ ┌─────────────┐ │ Cloud CDN │────▶│ Global │ │ (CDN) │ │ Load Bal. │ └─────────────┘ └──────┬──────┘ │ ┌──────▼──────┐ │ GKE │ │ Au