resonate-philosophy

To simplify durable workflows, refactor them into sequential generator functions using Resonate's yield* checkpoints. This leverages built-in retries and persistence, eliminating the need for external retry wrappers and status tables.

When using Resonate for state management, infrastructure patterns like status tables, retry wrappers, event buses, and distributed locks are unnecessary. Resonate's built-in durability and structured concurrency handle these concerns automatically.

To convert event-driven patterns into sequential generator-based workflows, replace distributed-systems logic with Resonate's yield* checkpoints. Rely on its crash recovery and structured concurrency to manage order processing and external API orchestration.

You do not need a status database for Resonate workflows. Resonate provides built-in persistence and crash recovery through yield* checkpoints, allowing you to eliminate external state duplication and redundant status tracking.

The best way to handle error-handling in durable workflows without over-engineering is to rely on Resonate's built-in retries. By using generator functions with yield* checkpoints, you avoid complex distributed locks and manual state duplication.

Your Resonate workflow likely has duplicated state management logic because it still relies on traditional distributed-systems patterns. Shifting to simple, sequential code with yield* checkpoints removes the need for external state duplication.