Handling non-functional requirements in .NET Core microservices
When you start making microservices, you need to make sure that they work in the expected state. The whole system should not become unavailable if parts of it fail, because in distributed systems there is a high probability that some component is down.
Also, in case of issues, you need a clean way to track back events that happened in the past, and use of debugger on the prod is not an option. In this session we will see a live demo of how to add health checks, logging, distributed tracing and resilience to .NET Core applications, and reduce risk of maintenance issues in the future.