When running your own orchestrator isn’t worth it anymore — and why EvenUp chose Temporal

EvenUp details their migration to Temporal, focusing on their use of `temporal_worker_task_slots_used` and latency-based metrics (`temporal_workflow_task_schedule_to_start_latency`, `temporal_activity_schedule_to_start_latency`) for scaling workers. They also describe implementing a Kubernetes liveness probe using metrics like `temporal_num_pollers`, `temporal_worker_task_slots_available`, and `temporal_request{operation="RespondWorkflowTaskCompleted"}` to automatically restart unhealthy worker containers, eliminating periodic processing slowdowns and on-call pages.