Business processes / 9 / 12
Notification delivery
A business app texts login codes, "invoice received" notices and payment receipts. Sending them inside the request ties the app to a slow provider. An outbox, a queue and a sender worker take the provider out of the request; then come rate limits, delivery receipts, a fallback chain with deadlines, dedup, user preferences, cost and a second provider.
- 14 min
- Intermediate
- 12 steps
- API p95 latency
- 320 ms
- Delivered
- 97 %
- Duplicate messages
- 0 /day
- Messaging spend per day
- 410 $
- request
- reply
- redelivery
- duplicate
- lost
Numbers are a model scenario, not measurements
The real request
Business API → SMS provider ARequest
POST /v1/messages HTTP/1.1
Host: sms-provider.example.com
Authorization1: hidden
{
"to": 2hidden,
"sender": 3"BIZAPP",
"text": "Your login code: ***. Valid 2 min.",
"client_ref": 4"otp_u42_7f3a"
}
Response
HTTP/1.1 200 OK
{
"message_id": "msg_90211",
"status": 5"accepted",
"parts": 61
}
Authorization· hidden — The app's API key at the provider. Hidden here.to· hidden — The phone number. Personal data: hidden here and masked in your logs too (+99890***4512).sender— The sender name the phone shows. Many operators accept only names registered in advance.client_ref— Our own id for this message. It comes back in the delivery receipt, so we can match the two.status—acceptedmeans the provider took the message into its queue. Not that the phone got it.parts— How many SMS segments were billed. A long or non-Latin text costs 2 or 3.
Build it yourselfCheat sheetCompare lessons
Course: 74 lessons
01 Foundations
02 Scaling
03 Data & storage
04 Communication
05 Reliability
06 Architecture
07 Security
08 Shipping
09 Whole systems
10 Business processes
11 Case studies