Skip to content
home about thoughts case studies projects specs skills rss

Series

Integration Without Illusions

What happens after an HTTP 200, during a retry, or when half the work succeeded? The boundary is only useful once those failures have names.

2018
  1. An HTTP 200 Does Not Mean the Operation Succeeded 01/01
  2. A Third-Party API Is an Unreliable Collaborator 01/02
  3. Validate at the Boundary You Control 01/03
  4. Map External Data Before It Enters Your Model 01/04
  5. A Webhook Delivery Is Not a Unique Event 01/05
  6. An Idempotency Key Is Not an Identity 01/06
  7. A Rate Limit Belongs to All the Workers Sharing It 01/07
  8. Retry Budgets Multiply Across Layers 01/08
  9. Partial Work Needs a Child Ledger 01/09
  10. A Cache Must Distinguish Empty from Unavailable 01/10
  11. Renaming a Field Is a Protocol Migration 01/11
  12. A Capability Interface Is Smaller Than a Vendor Client 01/12
© 2026 Brian Faust
· ·
·
Serein · Powered by Hugo