Bridging Pub/Sub to Temporal with Standalone Activities

What this post added

This post introduces and demonstrates the use of Temporal Standalone Activities as a mechanism to bridge external event sources (Pub/Sub) to Temporal Workflows. It highlights how Standalone Activities can replace complex custom retry and state management logic in event handlers, leading to simpler, more robust systems. The post provides code examples for both the Standalone Activity definition and its invocation from a client, emphasizing the importance of deterministic IDs and conflict policies for reliable execution and visibility in the Temporal UI.