resonate-http-service-design-typescript

Map ephemeral route handlers to durable Resonate workflows so long-running HTTP requests in TypeScript execute asynchronously in the background. This returns a 202 immediately while the workflow runs, ensuring the API server remains responsive and crash-safe.

Make HTTP API job submissions idempotent by using stable promise IDs for each workflow. Even if a client retries a request, the workflow executes only once, and any promise-exists errors are safely treated as idempotent outcomes rather than failures.

Structure RPC calls between services by decomposing your architecture into API, worker, and database groups. Invoke durable RPC methods between these groups to coordinate tasks securely, ensuring stable RPC targeting and consistent communication across the workflow lifecycle.

Webhook callbacks resolve approval promises within durable workflows to signal async job completion. External systems send webhooks to your API, which forwards the callback to the Resonate workflow, allowing the suspended promise to resume and complete the job lifecycle.

Ensure deterministic results in durable workflows by using ctx.date.now and ctx.math.random instead of native JavaScript functions. These deterministic APIs guarantee consistent execution during replays, preventing side effects from breaking workflow state during retries.

Yes, you can use this durable workflow pattern with Express or Fastify TypeScript servers. The pattern maps standard HTTP route handlers to Resonate workflows, fitting naturally into existing API server setups without requiring a complete framework rewrite.