How we built it: Running Replay on Temporal

This post details the architecture and implementation of a conference registration system for Temporal's Replay conference, built on Temporal. It highlights the use of Workflows for managing the entire lifecycle of an order and individual tickets, treating them as processes rather than database rows. The post emphasizes the use of Activities for interacting with external systems (payment processors, email APIs, databases) with configurable retry policies and idempotency keys. It also discusses the pattern of spawning a separate Ticket Workflow for each ticket, managed by an Order Workflow, and the use of Signals and Queries for external communication. The system demonstrates how Temporal handles long-running, stateful processes with complex event-driven logic, including waiting for events over months.