Google Cloud
Serverless
starter
Pub/Sub Queue-Worker — Google Cloud Architecture Template
An ingest function pushes jobs to Pub/Sub where an autoscaling Cloud Run worker processes them into Firestore and Cloud Storage.
Why this architecture works
- Buffering work in Pub/Sub absorbs traffic spikes without dropping requests.
- Cloud Run workers scale on subscription backlog and to zero when the queue is empty.
- At-least-once delivery plus idempotent handlers gives reliability without a heavyweight broker.
- Large payloads land in Cloud Storage while metadata stays queryable in Firestore.
What's inside (7 resources)
Ingest Fn
gcp-cloud-functions
Job Queue
gcp-pub-sub
Worker Service
gcp-cloud-run
Job Metadata
gcp-firestore
Results Bucket
gcp-cloud-storage
Cloud Logging
gcp-logging
Cloud Monitoring
gcp-monitoring
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.