Distributed Systems · Editable reference architecture
Durable execution architecture
An editable durable execution architecture reference showing Invocation → Execution coordinator → Event history. Replay deterministic decisions and isolate nondeterministic effects.
Open & Edit in DrawArc (Free, No Login Required)Your changes stay in a separate draft on this browser. Download an editable project to keep a portable copy.

7 components · 8 connections · Open the editor to zoom, move nodes and edit source.
Architectural overview
Durable execution architecture addresses the responsibilities and boundaries shown in this reference rather than prescribing an entire production deployment. The primary flow starts at Invocation and reaches Event history through Execution coordinator. Use this view to explain which component initiates work, which component owns a decision, and where a dependency can affect the caller. Replay deterministic decisions and isolate nondeterministic effects.
The diagram contains 7 distinct components and 8 directed relationships. A separate path connects Execution coordinator → Task worker → External operation. A separate path connects Task worker → Checkpoint → Event history. A separate path connects Event history → Recovery replay → Execution coordinator. These arrows describe logical interactions; they do not establish authentication, network access, atomic transactions or delivery guarantees. Label the actual protocol, payload contract and owner when adapting the drawing to your system. Keep synchronous and asynchronous boundaries explicit so that a reviewer can identify where a request ends and a later operation begins.
Before implementing this architecture, define expected load, data classification, latency budgets and recovery objectives. Give Invocation a bounded dependency timeout and a documented failure response. Assign ownership to any state or external service added during implementation. Validate the decision above against your workload instead of treating the presence of a component as proof of reliability. Open the editable canvas, replace generic labels with real deployment units, and document the decisions that differ from this reference.
The real-world problem
Design or explain durable execution architecture with explicit ownership and dependency paths. Replay deterministic decisions and isolate nondeterministic effects.
Data flow
Connections from this diagram. Branches and control signals are not a single chronological sequence.
- Invocation → Execution coordinator. Define the interaction contract and trace the resulting response or state change.
- Execution coordinator → Event history. Define the interaction contract and trace the resulting response or state change.
- Execution coordinator → Task worker. Define the interaction contract and trace the resulting response or state change.
- Task worker → External operation. Define the interaction contract and trace the resulting response or state change.
- Task worker → Checkpoint. Define the interaction contract and trace the resulting response or state change.
- Checkpoint → Event history. Define the interaction contract and trace the resulting response or state change.
- Event history → Recovery replay. Define the interaction contract and trace the resulting response or state change.
- Recovery replay → Execution coordinator. Define the interaction contract and trace the resulting response or state change.
Security boundaries
- Authenticate callers at the boundary before Execution coordinator accepts protected work; authorize the specific operation rather than trusting network placement.
- Use separate service identities and least-privilege permissions for Execution coordinator, Event history, Task worker. Encrypt sensitive traffic, protect credentials and avoid placing confidential payloads in logs.
- Validate untrusted inputs and restrict administrative/configuration endpoints separately from the main flow.
Failure handling
Invocation is unavailable or slow
Response: Apply bounded timeouts and controlled backoff only where retrying is safe. Return an explicit failure or durable acceptance; do not report success before required work is committed.
Verify: Interrupt Invocation in an isolated test and measure errors, recovery and any repeated side effects.
A dependency repeats or drops a request
Response: Use operation identifiers and explicit acknowledgement/reconciliation where needed. Verify idempotency before enabling retries.
Verify: Exercise the failure path with representative records and verify both the visible response and the resulting state.
An invalid or incompatible input reaches Execution coordinator
Response: Validate the input contract before effects are committed. Preserve rejected input identifiers without exposing secrets, and document a safe replay or correction procedure.
Verify: Send malformed and older-version inputs through Invocation and verify rejection, observability and unchanged valid state.
Trade-offs and alternatives
Replay deterministic decisions and isolate nondeterministic effects.
- Benefit
- Makes the ownership and interaction boundaries visible for a focused design review.
- Cost
- The 7 illustrated components still require contracts, monitoring and operational ownership; extra boundaries can add latency and failure modes.
- Alternative
- Use a simpler deployment when it meets the same requirements, or split a boundary only after measuring a specific need.
Logical boundaries versus deployment units in Durable execution architecture
- Benefit
- Keeps the responsibilities of Invocation, Execution coordinator, Event history visible without requiring a separate server for each box.
- Cost
- A logical view does not establish isolation, independent scaling or high availability; those require a separate deployment design and operational tests.
- Alternative
- Co-locate components in a simpler deployment first when ownership and workload requirements permit it.
When to use this architecture
- Explain durable execution architecture to engineers or stakeholders using a concrete visual flow.
- Review this decision before deployment: Replay deterministic decisions and isolate nondeterministic effects.
- Adapt a starting diagram for your own requirements, then record and validate every changed boundary.
Key components
- Invocation
- Invocation participates in durable execution architecture. Invocation → Execution coordinator. Define its contract, owner and access permissions in your implementation.
- Execution coordinator
- Execution coordinator participates in durable execution architecture. Invocation → Execution coordinator; Execution coordinator → Event history; Execution coordinator → Task worker; Recovery replay → Execution coordinator. Define its contract, owner and access permissions in your implementation.
- Event history
- Event history participates in durable execution architecture. Execution coordinator → Event history; Checkpoint → Event history; Event history → Recovery replay. Define its contract, owner and access permissions in your implementation.
- Task worker
- Task worker participates in durable execution architecture. Execution coordinator → Task worker; Task worker → External operation; Task worker → Checkpoint. Define its contract, owner and access permissions in your implementation.
- External operation
- External operation participates in durable execution architecture. Task worker → External operation. Define its contract, owner and access permissions in your implementation.
- Checkpoint
- Checkpoint participates in durable execution architecture. Task worker → Checkpoint; Checkpoint → Event history. Define its contract, owner and access permissions in your implementation.
- Recovery replay
- Recovery replay participates in durable execution architecture. Event history → Recovery replay; Recovery replay → Execution coordinator. Define its contract, owner and access permissions in your implementation.
Questions about this template
What does this durable execution architecture diagram show?
It shows 7 components with the core flow Invocation → Execution coordinator → Event history. Replay deterministic decisions and isolate nondeterministic effects.
Can I edit this diagram without signing in?
Yes. Open the template in the browser-local canvas to change nodes, connections and source. AI generation and cloud account storage require sign-in.
Is this a complete production implementation?
No. It is an editable reference. Validate the security controls, dependency behavior, capacity and recovery plan against your own requirements before implementation.
Validate your implementation
Use the relevant platform documentation to verify service limits, supported features and configuration. This diagram is an original reference rather than a reproduction of a provider deployment.