10
Building Resilient Microservices
In the previous chapter, we explored the saga pattern, which allowed us to orchestrate long-running business transactions across multiple services without compromising consistency. Sagas provide a crucial layer of fault tolerance for business workflows, but they are just the beginning when designing genuinely resilient systems.
Modern applications must be built to expect failure. In such systems, failure is not an anomaly but an operational certainty. Whether it’s a network timeout, a downstream service crash, a temporary infrastructure hiccup, or an unresponsive third-party API, your application must be engineered to handle failure gracefully. This chapter is dedicated to helping you design resilient microservices ...
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