The original title is "Temporal in Production: Sharp Edges & Good Practices"

Short summary

A senior engineer's guide to using Temporal for durable execution in production distributed systems, drawn from years building bank money-movement cores. Covers the core architecture (event history as source of truth, replay-based recovery), the critical separation between deterministic workflows and side-effecting activities, and a strong argument against cross-service workflow coupling. Recommends keeping workflows and activities within a single service boundary to avoid hidden deploy coupling between teams.

• •Keep all business logic and external calls in activities; workflows must stay deterministic for replay
• •Don't span workflows across services—use plain HTTP or Kafka calls instead to avoid hidden coupling
• •Event history is the source of truth; workers replay it to recover state after crashes

Generated with AI, which can make mistakes.