Excellent overview, this approach looks well worth implementing. One extra step I advocate is, where possible and once v2 has had time to settle in production, to replace the v1 implementation with one that maps from the v2 response to the old v1 response. This allows the code to keep moving forward without the burden of multiple possibly diverging implementations.
Hello Milan, great video. One question though is it possible to have a flags inside my application database, so I can just modify them in runtime? Or the only way is using appsettings or azure? Thank you.
Nice video. I assume this would be per running instance so does nto auto scale horizontally. We currently use Unleash for our feature flags. Is there an easy way to share the feature flag rollout details via a backplane like Redis?
Excellent overview, this approach looks well worth implementing.
One extra step I advocate is, where possible and once v2 has had time to settle in production, to replace the v1 implementation with one that maps from the v2 response to the old v1 response. This allows the code to keep moving forward without the burden of multiple possibly diverging implementations.
That's a really solid idea! I'll see if I can mention that in some future post or video.
I loved this video. Congrats! Top-notch content inside :)
Excellent as always. Thanks for all you do, Milan!
It's my pleasure!
Great Video Milan. I tried and extended with Azure App Configuration. Working perfectly. Thank you.
Glad to hear it's working well!
Hello Milan, great video. One question though is it possible to have a flags inside my application database, so I can just modify them in runtime? Or the only way is using appsettings or azure? Thank you.
Azure App Configuration is the preferred approach here, for easier maintenance. You could use a database - but probably with a custom implementation
Nice video. I assume this would be per running instance so does nto auto scale horizontally. We currently use Unleash for our feature flags. Is there an easy way to share the feature flag rollout details via a backplane like Redis?
Move the flags into shared config like Azure App Configuration
Do I just setup the targeting context accessor interface in DI with the implementation? How does feature management know about my implementation?
You say WithTarget< TargetingContext > th-cam.com/video/KWvSYrSdU44/w-d-xo.html
Excellent video!
Thank you very much!
Very nice as always
Thanks a lot
Believe me you are amazing 👏. More than official dotnet channels I learned more on your channel. Thanks for keeping your vedios free to watch😊.
Glad to hear it! More to come :)
Great Video as usual, Milan!
One question: Does the FeatureManagement work with Minimal APIs, instead of MVC Attributes on Actions?
Yes, it works fine - just with a custom middleware filter
This was great content.
Can you make a video on integration with Azure and AWS in the future?
Sure
Why you write records like classes? Shouldn't the records reduce the code ?
Yes and no
Did I miss something or will your caching never hit because you never enriched the items?
The caching is done by whatever calls the targeting context
Very nice :)
I'm glad you liked it!
Very goood
Thanks!
The first package seems pointless, the second package however is amazing.
Versioning is pointless? 😅
@@MilanJovanovicTech some people just upgrade thing to next version and get rid of old ones, no need versioning :)