Health monitoring and dependency injection - CNUG November 2019

Meetup: Copenhangen .NET User Group Location: Copenhagen, Denmark Abstract: * I don't feel so well… Integrating health checks in your .NET Core solutions * Do you have any idea how your ASP.NET Web Apps and APIs are functioning? Are they behaving healthily or in a degraded state? You might be able to tell from log information and telemetry data, but why not have them tell you how healthy they are themselves? ASP.NET Core 2.2 introduces health endpoints that let your apps and APIs do just that. In this session you will learn how to make health checks an integral part of your solution. We will cover various types of health checks ranging from internal status, such as memory thresholds, to health based on external dependencies, such as databases and HTTP endpoints. Finally, you are going to see how this all can be used in a Docker container cluster to allow the orchestrator to check for liveliness and readiness based on your health endpoints. * It depends: .NET Core dependency injection * The dependency injection system of .NET Core is very elaborate and allows for complex inversion of control scenarios. You will see the ins and outs of doing that, but also learn how to avoid mistakes that might be easy to miss. .NET Core comes with its own dependency injection system, that you probably know from ASP.NET Core. In this session we will have a detailed look at all of the specifics of Microsoft’s default DI system for .NET Core applications. You will learn how to properly use the Inversion of Control features, such as registering services, scopes, lifetimes, and how to resolve instances. Armed with this DI knowledge, we will revisit ASP.NET Core and investigate bootstrapping and typical scenarios for middleware, background processes and resolving objects from MVC and Razor. At the end there will be a deep dive into topics with service descriptors, implementation factories, do’s and don’ts and pitfalls to avoid memory leaks in your implementation.