The foundation: Why Temporal for a data pipeline?

What this post added

This post details the use of Temporal Standalone Activities to bridge a Pub/Sub event to a Temporal Workflow for a PII-compliant data pipeline. It explains how an `ingestion_handler` Activity, triggered by a Pub/Sub event, starts a `ComplaintWorkflow`. The post also outlines the functional and non-functional requirements of the pipeline and justifies the choice of Temporal for orchestration, highlighting its benefits in resilience, consistency, availability, and observability.