Reading a capture
Reading a capture somebody else produced
The thesis track: a generated client, a capture, and a defect that is invisible in the code.
A generated HTTP client with a retry loop, no jitter, no idempotency key and a fresh connection per request looks correct, passes its unit test, and at load becomes a retry storm, a TIME_WAIT exhaustion, or both. None of that is visible in the code.
It is visible in a capture. A handshake before every request means the pool is not reusing. The same request line arriving twice at the origin means a side effect happened twice. Retries landing on the same millisecond mean there is no jitter to spread them.
The skill is reading the capture, and the reason it is worth having is that the code will keep looking fine.
Predict
Which of these is invisible in the client's source and obvious in its capture?