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 “never down” at the same time.
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.
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
