vault / systems / go-workers.md

Go worker pools

System design 55 words 2 outgoing 1 backlinks

A bounded worker pool separates accepting work from doing it. The queue and worker limit make overload a visible choice: wait, reject, or shed work rather than spawn without limit. The firmware comparison in the post is about keeping handlers short and defining backpressure, not treating servers like microcontrollers.

Read the full example: related post.

LINKS IN THIS NOTE

[[ P95 latency ]] P95 describes the point below which 95% of measured request times fall. It says more about slow requests than an average, but still needs a workload and measurement window. A load-test result is not a promise about production traffic. Bounded... [[ Observability ]] For feedback investigation, record enough of the request to reconstruct what happened: the question, retrieval, response and relevant configuration. A trace helps connect those steps. Dashboards can show a pattern, but a concrete replay is often what tells us which...