JobHome · GCP · event-driven
Multi-client telephony data pipeline
Problem
Incoming calls from several service queues arrived through a telephony API and had to become per-client analytical tables, with no manual work for each new file, queue or client.
Solution
A Python extractor writes the raw payload to Cloud Storage. Triggering is automatic through Pub/Sub and Cloud Tasks: the bronze job, on Cloud Functions, receives the file path (bronze_uri) as a parameter. A queue → client map in an environment variable routes each record, and each client's tables are created automatically in BigQuery. Silver and Gold layers standardize and prepare the data for consumption, and all infrastructure is provisioned with Terraform.
Impact
- A new client or queue is added through configuration, with its table created automatically.
- Event-triggered processing, no manual runs.
- Reproducible, versioned infrastructure with Terraform.
Python / Cloud Storage / Pub/Sub / Cloud Tasks / Cloud Functions / BigQuery / Terraform


