Delivery Is a Routing Problem, Not a Messaging Problem
Why routing decisions influence delivery behavior far more than most messaging APIs expose.
May 24, 20267 min read
Command Palette
Search for a command to run...
Series
Programmable Messaging Infrastructure
Infrastructure notes on programmable messaging systems, delivery routing, carrier behavior, DLR pipelines, scalability and modern SMS infrastructure engineering.
The anatomy of message execution: what happens after your API returns 200 OK
A 200 OK response is often treated as completion. In many backend systems, it is not. It usually means one thing: the request crossed the API boundary successfully It does not always mean: the work f
May 1, 202619 min read56Why your logs say everything worked (even when it didn’t)
Your logs show success. Your system tells a different story.
Apr 25, 20264 min read65What your API already did before returning success (and why that matters)
The API returned success. The message was not delivered. Those are not the same thing. A request returning is not the same as work completing From the outside, sending an SMS looks simple: request →
Apr 20, 20263 min read66What actually breaks when messaging hits scale (and why APIs don’t show it)
High-volume messaging exposes routing behavior, queueing, latency and execution paths most APIs hide. Everything works. Requests return 200.Messages get accepted.Delivery looks consistent. Until it d
Apr 17, 20264 min read32Everything works. Until it doesn’t: what changes when messaging hits scale
High-volume messaging exposes routing behavior, latency and execution paths most APIs don’t show. Everything works. Requests return 200.Messages get accepted.Delivery looks consistent. Until it doesn
Apr 17, 20263 min read83