Google Cloud
Microservices
intermediate
Cloud Run Services + API Gateway — Google Cloud Architecture Template
Serverless microservices on Cloud Run fronted by API Gateway, with Firestore state and async notifications over Pub/Sub.
Why this architecture works
- API Gateway centralizes auth, quotas, and API keys so each service stays thin.
- One Cloud Run service per bounded context enables independent scaling and deploys.
- Firestore gives serverless, strongly consistent document storage with no capacity planning.
- Async work flows through Pub/Sub, keeping user-facing request latency low.
- Per-service IAM identities restrict every service to only the resources it owns.
What's inside (9 resources)
API Gateway
gcp-api-gateway
Service Accounts
gcp-iam
Users Service
gcp-cloud-run
Orders Service
gcp-cloud-run
Firestore
gcp-firestore
Order Events
gcp-pub-sub
Notification Service
gcp-cloud-run
Cloud Monitoring
gcp-monitoring
Cloud Logging
gcp-logging
From template to running infrastructure
- Open this template in the CloudForge visual designer (free account, no credit card).
- Customize resources, names, and connections on the drag-and-drop canvas — or ask Vani, the AI architect, to adapt it.
- Generate production-ready Terraform or Pulumi in one click.
- Review the plan diff and security scan, then deploy with human approval.