Eager Workflow Start optimal for short-lived workflows with local activities in first task
infoEWS is specifically designed for short-lived workflows that use local activities to interact with external services in the first workflow task. These workflows benefit most from reduced startup latency while maintaining reliability through server-driven retries and compensation.
Workflows that initiate external service interactions via local activities in their first task and complete within low tens of milliseconds are optimal candidates for EWS.
1. Identify workflows that fit the EWS profile: short-lived, external service interactions, local activities in first task. 2. Ensure workflows are deployed close to Temporal Server for network latency benefits. 3. Use local activities (not regular activities) for first-task external interactions. 4. Design workflows to initiate critical interactions immediately in first task. 5. Measure baseline latency before enabling EWS. 6. Deploy EWS for these specific workflow types and measure improvement. 7. Use cases include: financial transactions, collaborative apps with reliable replay, IoT control systems.