Streaming · Editable reference architecture
Exactly once processing architecture
An editable exactly once processing architecture reference showing Source log → Transactional processor → State checkpoint and downstream dependencies. State the exact boundary of the guarantee.
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.

6 components · 4 connections · Open the editor to zoom, move nodes and edit source.
Architectural overview
Exactly once processing architecture addresses the responsibilities and boundaries shown in this reference rather than prescribing an entire production deployment. The primary flow starts at Source log and reaches Transactional sink through Transactional processor, State checkpoint. Use this view to explain which component initiates work, which component owns a decision, and where a dependency can affect the caller. State the exact boundary of the guarantee.
The diagram contains 6 distinct components and 4 directed relationships. A separate path connects Checkpoint coordinator → Source offsets. 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 Transactional processor 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 exactly once processing architecture with explicit ownership and dependency paths. State the exact boundary of the guarantee.
Data flow
Connections from this diagram. Branches and control signals are not a single chronological sequence.
- Source log → Transactional processor. Define the interaction contract and trace the resulting response or state change.
- Transactional processor → State checkpoint. Define the interaction contract and trace the resulting response or state change.
- State checkpoint → Transactional sink. Define the interaction contract and trace the resulting response or state change.
- Checkpoint coordinator → Source offsets. Define the interaction contract and trace the resulting response or state change.
Security boundaries
- Authenticate callers at the boundary before Transactional processor accepts protected work; authorize the specific operation rather than trusting network placement.
- Use separate service identities and least-privilege permissions for Transactional processor, State checkpoint, Transactional sink. 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
Transactional processor 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 Transactional processor 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 Transactional processor
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 Source log and verify rejection, observability and unchanged valid state.
Trade-offs and alternatives
State the exact boundary of the guarantee.
- Benefit
- Makes the ownership and interaction boundaries visible for a focused design review.
- Cost
- The 6 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 Exactly once processing architecture
- Benefit
- Keeps the responsibilities of Source log, Transactional processor, State checkpoint 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 exactly once processing architecture to engineers or stakeholders using a concrete visual flow.
- Review this decision before deployment: State the exact boundary of the guarantee.
- Adapt a starting diagram for your own requirements, then record and validate every changed boundary.
Key components
- Source log
- Source log participates in exactly once processing architecture. Source log → Transactional processor. Define its contract, owner and access permissions in your implementation.
- Transactional processor
- Transactional processor participates in exactly once processing architecture. Source log → Transactional processor; Transactional processor → State checkpoint. Define its contract, owner and access permissions in your implementation.
- State checkpoint
- State checkpoint participates in exactly once processing architecture. Transactional processor → State checkpoint; State checkpoint → Transactional sink. Define its contract, owner and access permissions in your implementation.
- Transactional sink
- Transactional sink participates in exactly once processing architecture. State checkpoint → Transactional sink. Define its contract, owner and access permissions in your implementation.
- Checkpoint coordinator
- Checkpoint coordinator participates in exactly once processing architecture. Checkpoint coordinator → Source offsets. Define its contract, owner and access permissions in your implementation.
- Source offsets
- Source offsets participates in exactly once processing architecture. Checkpoint coordinator → Source offsets. Define its contract, owner and access permissions in your implementation.
Questions about this template
What does this exactly once processing architecture diagram show?
It shows 6 components with the core flow Source log → Transactional processor → State checkpoint → Transactional sink. State the exact boundary of the guarantee.
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.