Always-on software systems are the expectation, not the exception.
In today's digital world, stakeholders and users expect software systems to be available 24/7.
Downtime can lead to lost revenue, productivity and customer satisfaction.
Therefore, it's important to design and develop software systems that are resilient to failures.
The good news is that there are a number of proven tactics and software architecture tips that can help you achieve a resilient software system.
In this post, I present some of the most important software architecture tactics to improve the resilience of the software system.
The recommended book "Continuous Architecture in Practice: Software Architecture in the Age of Agility and DevOps" has helped me a lot to write this post.