Why failures will hit you at the application level
In the previous post, we discussed availability, and how more nodes and the effects of remote communication affect it negatively. We learned that failures in today’s distributed, highly interconnected system landscapes are unavoidable and that we need to embrace them if we want to create highly available solutions.
Why your systems will fail for sure
In the previous post, we discussed what distributed systems mean in terms of failure modes that can occur and what their concrete consequences are regarding application behavior.
The effects of distribution
In the previous, introductory post why we need resilient software design, we discussed the stepwise journey from isolated monolithic applications to distributed system landscapes where applications continually communicate with each other. We also discussed that the number of peers involved continually grew (and still grows), while the update propagation duration expectations became shorter and the availability expectations went to…
The rise of distributed systems
In this post series, I will discuss what resilience means for IT systems and why resilient software design has become mandatory.
Are they the same thing?
In this post, I will discuss if there is a difference between resilience and fault tolerance when talking about IT systems.
Web site and blog. Writing about IT most of the time.
I'm Uwe, travelling the world of IT for many years. Worked in many roles in and around IT. Sharing my thought, ideas and insights here. Explorer. Connector. Sharer. Coder. Writer. Human. More. Order may vary.
Learn More
