Pick a number, any number. Most teams pick 200, or 'number of cores times 2,' or whatever the framework default is, and ship. The right number isn't a guess -- it's derivable from Little's Law and the ratio of CPU to wait time. Get it wrong and your service either wastes resources or quietly queues requests until it falls over.
Engineering Craft
TypeScript, CI/CD, databases, observability -- the skills that make code production-ready.
