TCC: Try, Confirm, Cancel¶
Reserve resources first, then durably confirm or cancel every reservation.
flowchart LR
J[Junior: why reserve] --> M[Middle: state transitions] --> S[Senior: phase failures] --> P[Professional: reservation scale]
flowchart LR
Try --> Decision{Global decision} --> Confirm
Decision --> Cancel
| Level | Guide | You are done when |
|---|---|---|
| Junior | Definition and why | You can explain provisional reservation. |
| Middle | How it works | You can implement idempotent state transitions. |
| Senior | Failures and mistakes | You can handle reordered phases and expiry. |
| Professional | Best practices and scale | You can operate reservation protocols at scale. |
Practice rule: Treat Confirm and Cancel as durable terminal choices, not best-effort callbacks.