How Azure App Configuration helps developers roll out new features | Azure Friday

Thank you 😊

Great session

this config service is pretty nice BUT what I think is bad is the example presented... the decision between beta / preview and prod version should have come on a reverse proxy level / load balancer level and not in app code. It will make the code more complicated. I can see other use cases for this service though

This was great, I am wondering what the code looked like for determining the user name and/or group membership and how the feature was then enabled for these specific users?

print("Its Just awesome.")

What about other language app? like Vue?

Is this architecture is in fact based on pull config data on every hit to default page? This seems terrible ineffective if application has to query remote configuration store on every hit

Does libarry include management sdk? So Can I modify those feature toggles from my code if i need to ?

One thing he didn't touch on for the auto refresh of Azure App Config is that I thought you needed to specify a sentinel value that when changed triggers the refresh. Or is that not required anymore?

Porque borraste el five nights at freddy gratis porque ponlo de nuevo porfaaaaaaaaa escrive en español o pon yes o nou

How can we use feature flags in AKS and containers ? any useful resource to look at ?

Great video. Definately going to be trying to get authorisation to use this in a future release of our software

how feature management works with azure functions? I didnt notice in startup class reference to config. service connection string