question

JonesIke-4961 avatar image
0 Votes"
JonesIke-4961 asked kobulloc-MSFT edited

App Configuration Best Practices for Frontend?

I am wanting to use App Configuration to store both configuration and feature flags (using the Feature Manager) for both Frontend and Backend. Frontend is in Angular and Backend is .NET Core Web API. They run on separate App Services. I understand how to use the Feature Manager for the Backend but I don't see any guidance or npm package for the end. I see the REST APIs for App Configuration, but I am worried about the frequency of the calls and also exposing the entire configuration settings to the Frontend.

Is there any guidance or npm package I should be referencing/using?

azure-app-configuration
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

JavierSotoCarujo-9413 avatar image
0 Votes"
JavierSotoCarujo-9413 answered JonesIke-4961 commented

Hello,

I think on this guide you would find all the basic topics you´ll need into your journey:

https://docs.microsoft.com/es-es/learn/certifications/exams/az-204

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

No thats just a link to the certification exam.

1 Vote 1 ·
kobulloc-MSFT avatar image
0 Votes"
kobulloc-MSFT answered kobulloc-MSFT edited

Edit: Lisa Guthrie works with the product group and I would refer to her answer below.

For client-side usage, we recommend building a server-side component to handle communication directly with App Config. Then have the client app communicate with that server-side component, to load the configuration it needs.

This reduces the load on (and therefore the cost of) App Config, since the server-side component can cache configuration appropriately, then serve to multiple clients out of the cache. Versus a model where the clients hit App Config directly, in which case, they each have their own cache rather than sharing.

This also allows you to avoid exposing the entire configuration to the clients, if that's important.

Additional references:

Official best practices
Documentation

Azure SDK for JavaScript
https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/appconfiguration/app-configuration

REST API
https://github.com/Azure/AppConfiguration#rest-api-reference










5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

LisaGuthrieMSFT-0286 avatar image
1 Vote"
LisaGuthrieMSFT-0286 answered

For client-side usage, we recommend building a server-side component to handle communication directly with App Config. Then have the client app communicate with that server-side component, to load the configuration it needs.

This reduces the load on (and therefore the cost of) App Config, since the server-side component can cache configuration appropriately, then serve to multiple clients out of the cache. Versus a model where the clients hit App Config directly, in which case, they each have their own cache rather than sharing.

This also allows you to avoid exposing the entire configuration to the clients, if that's important.

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.