Worked case · Failure and stress · 12 figures

Instant-transfer status path

Fast rails change control timing

Figure 01 / 12

Dependencies form a critical path

Dependencies form a critical path — Instant-transfer status path. Illustrative service dependency graph. Exact values are in the figure data below.
Illustrative service dependency graph

The case examines fast rails change control timing. Each edge is a required handoff in this illustrative path. A service can respond quickly while a downstream effect remains incomplete, so health needs both technical and business evidence.

Figure data and text version
FromToHandoff
Instant-transfer status pathDecision serviceAction request
Decision serviceEvidence providerRequired evidence
Decision serviceState storeDurable decision
State storeEffect publisherPending effect
Effect publisherExternal railFinancial action

A fast transfer can leave the sender while the platform waits for an acknowledgement. A timeout says the reply is missing, not that the financial action failed.

The integration retries a timed-out action with a new business identifier.

All amounts, rates, capacity limits, and outcomes in this case are synthetic. The three conditions are separate assumptions for comparison. A better result in the response condition is not measured proof that the proposed control causes that improvement. The figures expose the calculation and its limits; a real deployment needs its own evidence.

Read the result

210 intended requests generate 378 processing attempts under this retry assumption. Capacity is 135 attempts per interval, and the critical path consumes 305 ms of a 180 ms budget. The request-based SLO view observes 3000 bad requests against an illustrative allowance of 100. These measurements must be connected to the financial effect and control evidence before declaring recovery.

Model inputs and calculated values

Inputs below are the case-specific values. Each figure states the condition-specific assumptions and units used in its calculation. Calculated values are rounded for display.

InputValue
arrivals210
capacity245
budgetMs180
Calculated valueResult
arrivals210
attempts378
capacity135
latency305
budget180
remaining-125
window100,000
bad3,000
allowed100
Figure 02 / 12

Allocate the latency budget explicitly

Allocate the latency budget explicitly — Instant-transfer status path. Milliseconds on one critical path. Exact values are in the figure data below.
Milliseconds on one critical path

The four stages total 305 ms against a 180 ms budget, leaving -125 ms. Negative remaining time means this modeled path exceeds the target before adding any unmodeled overhead. The values are fixed teaching observations, not a latency guarantee.

Figure data and text version
StageMilliseconds
Ingress25
Feature reads55
Control evaluation180
Commit and response45
Remaining budget-125
Figure 03 / 12

A slow minority changes the tail

A slow minority changes the tail — Instant-transfer status path. Milliseconds; explicitly constructed percentile profile. Exact values are in the figure data below.
Milliseconds; explicitly constructed percentile profile

The constructed distribution separates the median from high percentiles. Percentiles are order statistics over the same request population; summing stage p99 values is not generally the service p99. This chart is a teaching profile, not a measured production distribution. Horizontal positions are the labeled observations or scenarios; equal spacing does not imply equal numerical increments.

Figure data and text version
PercentileLatency ms
p50214
p75274
p90336
p95427
p99702
Figure 04 / 12

Retries increase attempted work

Retries increase attempted work — Instant-transfer status path. Attempts per interval. Exact values are in the figure data below.
Attempts per interval

210 original requests produce 378 attempts under the stated average retry multiplier. The additional 168 attempts consume capacity even when their financial effect must remain idempotent. This simple model omits recursive retry storms across multiple layers.

Figure data and text version
Attempt typeCount
Original requests210
Additional attempts168
Figure 05 / 12

Attempted demand versus capacity

Attempted demand versus capacity — Instant-transfer status path. Attempts; measures are not all additive. Exact values are in the figure data below.
Attempts; measures are not all additive

The interval has capacity for 135 attempts against 378 attempted requests. The difference is 243 unserved attempts in this simplified window. An unserved attempt is not necessarily an unexecuted business action: reconcile the stable action identifier before retrying a financial effect.

Figure data and text version
MeasureAttempts
Attempted demand378
Processing capacity135
Served this interval135
Unserved this interval243
Figure 06 / 12

Overload leaves a durable backlog

Overload leaves a durable backlog — Instant-transfer status path. Attempts waiting at interval end. Exact values are in the figure data below.
Attempts waiting at interval end

The six intervals use explicitly varied arrival multipliers and constant capacity. The queue carries forward unfinished attempts. Real systems also need a maximum age, admission policy, and expiry semantics so delayed work does not execute after its business authority has ended. Horizontal positions are the labeled observations or scenarios; equal spacing does not imply equal numerical increments.

Figure data and text version
IntervalPending attempts
T1130
T2335
T3691
T41,199
T51,518
T61,685
Figure 07 / 12

Throughput can stay flat while demand rises

Throughput can stay flat while demand rises — Instant-transfer status path. Attempts per interval. Exact values are in the figure data below.
Attempts per interval

The completion count is limited by available work and capacity. A saturated completion line with a growing queue is evidence of overload, not stable end-to-end service. Inspect waiting time and customer outcomes alongside throughput. Horizontal positions are the labeled observations or scenarios; equal spacing does not imply equal numerical increments.

Figure data and text version
IntervalAttemptsCompletions
T1265135
T2340135
T3491135
T4643135
T5454135
T6302135
Figure 08 / 12

Write state and pending effect together

Write state and pending effect together — Instant-transfer status path. Illustrative reliable handoff. Exact values are in the figure data below.
Illustrative reliable handoff

This sequence describes a transactional outbox within one datastore boundary. The publisher can deliver more than once, so the consumer also needs duplicate handling. A durable local handoff does not create a universal exactly-once guarantee across an external payment system.

Figure data and text version
EventCommit boundaryEvidence
Validate actionBefore transactionStable action key and permitted operation
Write state and outboxOne local transactionBoth records commit or neither does
Publish effectAfter commitDelivery may be retried
Consume effectConsumer boundaryIdempotent handling and stored result
ReconcileIndependent checkExpected and observed effects agree
Figure 09 / 12

Repeated delivery and financial effects differ

Repeated delivery and financial effects differ — Instant-transfer status path. Counts at different boundaries. Exact values are in the figure data below.
Counts at different boundaries

The example contains 378 transport attempts for 210 intended business actions. The protected effect count cannot be inferred from transport success alone. The table states the intended contract and the evidence needed to check it.

Figure data and text version
MeasureIllustrative valueRequired evidence
Business actions210Stable unique action identifiers
Transport attempts378Delivery identifiers and retries
Permitted effects210One effect per authorized action
Observed effectsMust reconcileAuthoritative ledger or external record
Figure 10 / 12

An SLO budget is a measured allowance

An SLO budget is a measured allowance — Instant-transfer status path. Request-based illustrative SLO; one measurement window. Exact values are in the figure data below.
Request-based illustrative SLO; one measurement window

For 100,000 eligible requests and a 99.9% illustrative SLO, the budget is 100 bad requests. This case observes 3000. Eligibility, success, and measurement windows must be fixed before interpreting the result. An SLO allowance never overrides a legal or financial correctness requirement.

Figure data and text version
MeasureRequests
Eligible population100,000
Bad requests allowed100
Bad requests observed3,000
Remaining budget-2,900
Figure 11 / 12

Dependency failures require scoped behavior

Dependency failures require scoped behavior — Instant-transfer status path. Dependency-specific policy boundary. Exact values are in the figure data below.
Dependency-specific policy boundary

The dependency is receiving institution. The response depends on the operation, required control, and evidence available. The table gives illustrative behavior classes, not a universal fail-open rule.

Figure data and text version
Failure stateIllustrative responseEvidence to retain
Optional signal lateUse approved degraded policyMissing signal and selected policy version
Required control unavailableHold the affected actionPending owner and expiry
Unknown external outcomeQuery and reconcileOriginal external action identifier
Publisher retryRepeat delivery safelyStable business key and attempt history
Figure 12 / 12

Recovery ends with a reconciled population

Recovery ends with a reconciled population — Instant-transfer status path. Business recovery sequence. Exact values are in the figure data below.
Business recovery sequence

The last successful health probe does not close the incident. Recovery must classify affected actions, resolve unknown outcomes, restore required controls, and verify money and records. A replay is allowed only under the action’s current authority and idempotency contract.

Figure data and text version
StageCompletion evidence
ContainThe integration retries a timed-out action with a new business identifier.
ClassifyKnown success, known failure, unknown outcome
ResolveRepair or replay by stable action identifier
VerifyCounts, amounts, and control evidence reconcile
CloseOwners accept remaining exceptions explicitly

Connect the result to the system

Keep the original action identity, query its status, and reconcile before creating another effect.

Check the population, evidence, permitted action, and actual effect together. A balanced calculation can still use the wrong population; a successful response can still leave an unknown financial outcome. The case’s numerical result applies only to its stated assumptions.

Sources and further reading

The chapter sources support the concepts and scope. They do not prescribe the synthetic model rates.

  1. Federal Reserve: payment systems
  2. Federal Reserve: Fedwire finality and settlement
  3. OFAC: A Framework for Compliance Commitments