Implementing resilient applications with an API Gateway

We know that API services fail due to any number of reasons, such as networks issues, connection (failed to open a connection to a data source like a SQL Server database) and API performance issues, failure to authenticate to dependencies, outage of a shared dependency, crash because of critical bugs, memory leaks and many more. In such scenarios, our services should be resilient enough to deal with predictable failures when they happen before they become more significant headaches than they need to be. Dealing with single server failures is more effortless, as the number of applications grows, you face new challenges in monitoring the health of each microservice to understand how your microservices-based application behaves when any of them becomes unavailable.

In this talk, we are going to present briefly how we can improve the stability and resiliency of a .NET application with the help of an API Gateway. Considering the fact that the modern API Gateway supports almost all modern resiliency patterns like timeouts, fallbacks, retry, health check endpoints, and circuit breakers.

Speaker: Bobur Umurzokov