>High availability, fault tolerance, always-on architectures are very difficult to achieve and maintain. Ironically, the only reason this is true is because ge

>High availability, fault tolerance, always-on architectures are very difficult to achieve and maintain. Ironically, the only reason this is true is because generally people working on those pretty much cobble shit together instead of writing correct code, so you have subsystems of code talking to subsystem of code, and inevitably shit goes wrong. Build your system correctly to the use case, from the ground up, and you will have a much easier time. Of course the counter argument to this is the age old "what if developers make mistakes, its better to use off the shelf software thats already tested and verified". But the real answer to that isn't to use off the shelf software, its to not be or hire shit developers.