Conclusion Failover mechanisms are neither an extra effort nor an extra cost that can be ignored in software solutions. From the developer’s perspective failover mechanisms are a sign-off: Understanding of working environment of a specific piece of code, Willingness to supply a reliable and robust system, A way to avoid irresolvable issues. On the other … Continue reading Software Failover: The jump-sheet for everyone – Conclusion

Why I lost my work? One of the frustrating aspects of utilising a digital system is when the system experiences an unexpected behaviour. It is frustrating, as all the work previously done tends to get lost and has to be done all over again. In the early years of word processing, the auto-save feature or … Continue reading Software Failover: The jump-sheet for everyone – Part III

My technical design is flawless It is a well known fact that developers tend to consider their product as their perfect creation. Thus, it is very difficult for them to understand that there might be scenarios that can occur, although not explicitly specified in requirements. The next sections show why introducing failover mechanisms does not … Continue reading Software Failover: The jump-sheet for everyone – Part II

Introduction A step in the project lifecycle is requirements gathering. During this stage in the project lifecycle the operation conditions are defined for the code that will be developed. However, whichever project management model is adapted, requirements are meant to change. Craig Brown in his articles on Better Projects has suggested that on average requirements … Continue reading Software Failover: The jump-sheet for everyone