A singleton SELECT - is this always the best solution for readability and performance? The article discusses a simple scenario, that shows that a singleton SELECT can result in surprising application behavior if not used properly.
A good application should be a good citizen in the environment it is living in. Applications must also cope with situations where some of the actions (like updating rows) may fail because of other applications doing the same task.
We live in a massively multithreaded world. Lots of actions are occurring around us. We are jumping from one task to another. Every now and then, we have to slow down and stop what we are doing to let another task make its way in the stream of activities. That task isn’t necessarily ours.