In the previous article, we introduced the Retry Pattern for recoverable failures. However, what do we do when a failure isn't recoverable? This article will look at the Circuit Breaker Pattern and how it applies to failures.
All applications, regardless of their architecture, must embrace the idea that failure is an option. We can count on hardware and networks to fail, so we must code for these failures. However, most failures are not terminal. Given sufficient time, many failures are recoverable. In this article, we introduce the Retry pattern as an approach to gracefully recover from failure.
When building microservices applications, it is not practical to expose individual services directly to the application client. Instead, it is often advisable to introduce a mediator between the client application and its desired services. In this article, we present the "API Gateway" pattern.
How does a client find its service in a microservice application where we have elasticity and dynamic deployment? In this article, we introduce the Service Discovery pattern to address this problem.
Microservices not Monoliths.
ThinkMicroservices.com is a resource for understanding Microservices.
© ThinkMicroservices.com. Sitemap.
