distributed systems

Why we need resilient software design - Part 4

Why failures will hit you at the application level

Uwe Friedrichsen

9 minute read

Meadow (seen in northern Germany)

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.

Uwe Friedrichsen

9 minute read

Rape field (seen in northern Germany)

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.