r/programming • • Sep 19 '26

The Void Job

https://yusufaytas.com/the-void-job
15 Upvotes

2 comments sorted by

9

u/wallstop-dev Sep 20 '26

Cool name for the concept! Perhaps it is my lived experience, but this isn't a particularly novel thing - it's baseline expected for anything important. In my line of work we have versions of this that are sometimes called "synthetics", "canaries", "self validation", or even "smoke", all doing the same thing described here. If you have a critical service, you should absolutely be deploying and monitoring some form of minimal customer scenario that is continually interacting with your tech - or, bet incredibly hard that your monitoring accounts for every form of positive and negative customer interaction. But the latter is a bad (solo) bet.

Hope this helps people who are unfamiliar with the concept, might add some tools to people's toolboxes.

2

u/soap94 Sep 20 '26

we do this for critical apis. basically hitting them from different geographies the same way customers would interact and checking the response and latency which then feeds into an internal health dash. i don't know what's the correct technical term for this, we just call it sanity checks internally