Chapter 16. Conclusion
Over this book’s first 15 chapters, I have shared a mix of concrete practical advice and discussion of larger themes related to building resilient distributed systems. Given that we are at the end of this journey together, I thought now would be the perfect time to recap some of the major themes of the book before summarizing some of the patterns and practices we looked at.
Distributed Systems
The systems we build are distributed—multiple computers communicating over networks that cannot be 100% reliable. This means we have to embrace three fundamental truths with any distributed system we build:
-
You cannot beam information instantaneously between two points.
-
Sometimes you can’t reach the thing you want to talk to.
-
Resource pools are not infinite.
While these rules are simple and easy enough to understand in isolation, as the system becomes more complex, the implications of these rules give us a number of headaches.
Resilience Engineering
Trying to make sure nothing ever goes wrong is a problem if that’s all you do. You can’t control everything, and the unexpected will happen. Resilience engineering is all about accepting that fact and focusing instead on making sure that as many things go right as possible.
David Woods gives us four concepts for resilience that are woven through this book:
- Robustness
-
The ability to absorb expected issues, such as handling a machine crashing
- Rebound
-
Recovering after a traumatic event
- Graceful extensibility ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access