Communication / 5 / 6
Reliable callbacks
Another system sends you a message. What it takes so the message is never lost, never handled twice and never slows you down.
- 12 min
- Intermediate
- 9 steps
- Incoming
- 40 /s
- Reply p95
- 3 800 ms
- Lost
- 0 %
- Handled twice
- 0 /min
- request
- reply
- redelivery
- duplicate
- lost
- call: the reply returns on the same line
Numbers are a model scenario, not measurements
The real request
Sender → APIRequest
POST /callbacks HTTP/1.1
Host: api.example.com
Content-Type: application/json
X-Signature1: hidden
{
"event_id": 2"evt_81c2",
"type": "document.accepted",
"document_id": "doc_5521",
"sent_at": "2026-11-17T09:14:03Z"
}
Response
HTTP/1.1 200 OK
X-Response-Time3: 3812 ms
X-Signature· hidden — The sender signs the body so you can tell a real callback from a forged one. A secret, so it stays hidden here.event_id— The sender's own ID for this event. It stays the same on every retry, which matters later.X-Response-Time— Almost four seconds. If the sender gives up at three, it already sent the callback again.
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