Database Connection Pools Need a Budget Across Every Instance
A pool of ten connections sounds small until twenty application instances each have one.
wade womersley – york based software engineer
Engineering notes from the sharp end
wade womersley – york based software engineer I write the way I work: direct, useful, and more interested in what holds up in production than what sounds clever on a slide.
325 published posts
Latest update
Latest post
A pool of ten connections sounds small until twenty application instances each have one.
Archive
Readiness and liveness answer different questions. Connecting both to every dependency can make an outage harder to recover from.
The tin promises a biscuit. The buttons inside appear to consider that somebody else’s problem.
Retries at several layers can turn one failing request into a surprising amount of traffic.
Leaving a field out and deliberately clearing it are different requests. A partial-update endpoint needs to preserve that distinction.
The rare potion is staying in the bag. There might be a more important emergency after this emergency.
A successful backup job tells you something useful. Restoring it and running the application tells you considerably more.
Two people can save valid changes and still overwrite each other. A version check gives the application a chance to catch it.
The dependencies in a CI workflow deserve the same attention as the packages in the application it builds.
A sofa improves when one of its residents is a slightly ridiculous plush animal.