René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Secret loading is sequential and missing pre-emptive authentication","articleBody":"### Summary\n\nWhile using the library to load App Configuration, I’ve observed slow performance due to two key issues:\n\n- Secrets are fetched from Key Vault **sequentially**\n- No **pre-emptive authentication** is performed\n\n### Investigation\n\nThis behaviour was identified using Application Insights, with traces collected via OpenTelemetry on a Node.js process.\n\nBelow is an example trace showing a single configuration lookup referencing 14 secrets (which are stored in 4 x separate vaults):\n![Image](https://github.com/user-attachments/assets/07ae5152-da00-4b1a-ba52-e6687bcc2aa4)\n\nThe `loadConfig` trace wraps the point we call the `load` function: https://github.com/Azure/AppConfiguration-JavaScriptProvider/blob/5c1f4a34475fe94326228f8bdffaa8088779a2d6/src/load.ts#L28\n\nEach secret fetch initially results in a 401 (unauthenticated), followed by a successful retry after authentication. This happens for every unique Key Vault endpoint used.\n\nDespite the environment running within Azure, the full configuration load takes approximately **2 seconds**, introducing noticeable latency.\n\n### Expected behaviour\n\nPerformance could be improved significantly if:\n\n- Secrets were fetched **in parallel**\n- Authentication was performed **proactively**, avoiding repeated 401/retry cycles","author":{"url":"https://github.com/ronfor","@type":"Person","name":"ronfor"},"datePublished":"2025-04-30T13:07:00.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":7},"url":"https://github.com/191/AppConfiguration-JavaScriptProvider/issues/191"}