Specification · 04
Collection and routing
Where each event is captured, how it is checked and which systems receive it.
When this is useful
Different uses require different delivery times and data. A report updated overnight and a live workflow may not need the same route.
My contribution
I specify capture and delivery rules, including what happens when a record arrives late, fails validation or is sent more than once.
A constructed trace shows a warehouse commit followed by an acknowledgement timeout and a deduplicated retry; the support payload forwards only order ID and derived paid status.
What it covers
- Client and server capture points
- Schema and permission checks
- Destinations and required transformations
- Delivery requirements and acceptable delay
- Duplicate or rejected events, retries and replay
- Permission to add or change a destination
The output
A routing specification with checks, transformations, timing requirements and failure handling.
For an enquiry, describe the question and the systems involved.
contact@fiftystork.com ↗