SQL: Code for errors and be pleased when they don't occur
I spend a lot of time in large organizations that have spent an absolute fortune on highly-available systems, yet when those systems fail over (just as they were designed to do), most of the applications in the building break.
Why?
Because the developers have assumed that nothing ever breaks and have written their code in a far too optimistic manner. Did they do their jobs?
No
Is it possible for their next layer of code to deal with, say, a server disappearing for a few seconds? Of course it is. But it’s not going to happen by accident. It’s even more important in a cloud-based world.
2018-02-09