
When running your own orchestrator isn’t worth it anymore — and why EvenUp chose Temporal
3/17/2026
This post details how EvenUp migrated their existing workloads to Temporal. They specifically highlight their use of Temporal's metrics for scaling workers, employing both slot-based scaling using `temporal_worker_task_slots_used` and latency-based fallbacks with `temporal_workflow_task_schedule_to_start_latency` and `temporal_activity_schedule_to_start_latency`. Additionally, they describe the implementation of a Kubernetes liveness probe using metrics like `temporal_num_pollers`, `temporal_worker_task_slots_available`, and `temporal_request{operation="RespondWorkflowTaskCompleted"}` to automatically restart unhealthy workers, resolving issues with stuck workers and periodic processing slowdowns.


