Topic
Outbox and Inbox
A reliability pattern once side effects stop being local.
Outbox and inbox are less about queues and more about recovering integrity when write boundaries split across systems.
Prerequisites
No formal prerequisites. This is a valid starting topic.
Why this topic matters
Teams adopt asynchronous flows quickly, then discover that duplicate delivery, retries, and partial failure demand far stricter reasoning.
Primary article
Outbox and Inbox Without Magical Thinking
Where the guarantees actually come from, what still breaks, and how mature teams keep the pattern honest.
What you get
Move from topic framing into the full long-form reading experience with diagrams, tradeoff framing, and premium editorial packaging.
Diagram preview
Write boundary and message durability
Step 01
App write
Step 02
Outbox persistence
Step 03
Relay publish
Step 04
Inbox dedupe
Why it is here
A simple flow that makes the retry window and duplicate handling visible.