Skip to main content

ASP.NET Core - IOptionsMonitor vs IOptionsSnapshot

While preparing some training material about ASP.NET Core, I was wondering about the difference between IOptionsMonitor and IOptionsSnapshot. In contrast to IOptions allow both interfaces to track configuration changes during the lifetime of your application.

However, internally both interfaces are constructed completely different; IOptionsMonitor is registered in DI container as singleton, it has a CurrentValue property and is capable of detecting changes through OnChange event subscription. On the other hand, IOptionsSnapshot is registered as scoped, has a Value property and also have a change detection capability by reading the last options for each request, but it doesn't have the OnChange event.

So what’s the point of having 2 interfaces with completely different signatures when both achieve the same goal; picking up configuration changes at runtime?

The difference between the two (and this also explains the different implementation approach) is that IOptionsSnapshot guarantees that you have the same configuration values during a single request(explaining the scoped lifetime). IOptionsMonitor picks up every change immediately meaning that if the configuration value is read multiple times in a request, it can return different values.

As a general rule, you should prefer IOptionsSnaphot above IOptionsMonitor.

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...