Azure Function is not creating the new resources and environment for each request when using the docker container

Elizaveta Omelyusik 26 Reputation points

When deploying a docker container to Azure Functions it is supposed that azure will create new resources on each request so that the environment for each request will not overlap.
But it turns out that each request is processed by the same container.
Could you please clarify how to use the Azure Function with the independent environments (so that each request is handled in its own container)?

Azure Functions
Azure Functions
An Azure service that provides an event-driven serverless compute platform.
4,503 questions
{count} vote

Accepted answer
  1. Pramod Valavala 20,606 Reputation points Microsoft Employee

    @Elizaveta Omelyusik This is the expected behavior since a single container can handle many requests and would eventually scale out as many more requests come in at the same time. Or if each request is compute intensive, then that could trigger a scale out as well.

    If your scenario demands lower concurrency, you could tweak the host.json settings for HTTP to reduce the number of requests handled per instance, forcing it to scale out.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful