Join Chander Dhall for an in-depth discussion in this video Graceful degradation, part of Microservices and Azure Service Fabric Basics for Developers.
- [Instructor] Graceful degradation. There will be times when a service will have dependency on one or more than one services. If one of the dependent service dies, the current service should know how to handle the failure gracefully. So for example, if the wire transfer service is down, you don't want to leave the customer hanging. You should be able to understand the actual problem and communicate smartly to the customer. We can surely code both the monolithic as well as the microservice to fail gracefully.
However, the benefit of microservice is that since these are services that can be scaled independently, it's very rare that all of these will be down at the same time. So we could use some kind of retry logic. We can usually recover. We can also add some logic to fail gracefully. With this approach, the chance of failure is greatly reduced.
- Reviewing microservices vs. monolithic architecture
- Reviewing microservices and Azure Service Fabric basics
- Programming model architecture
- Creating a stateless service and a stateful service
- Creating a cluster in Azure
- Adding security to a cluster
- Finalizing cluster creation
- Deploying to an Azure cluster
- Debugging an application remotely