Azure app service capacity

Question

Hi ,

We have a third party application (WAR distribution) has to be deployed into Azure App service. Predominantly we are planning to use Tomcat 8.5 & Java 1.8 as platforms of our choice. Currently the application is running in on-primes data center with capacity of 4 CPU and 16 GB RAM with multiple instances of app running behind load balancer (LB).

Therefore we would like to know how much maximum and minimum threshold size of CPU and RAM the Azure App service supports today to run an application ? What is the memory footprint supported ? The application has setup configured for HTTP Session to store user identity. Is Azure app service supports sticky sessions and whether the user session will be distributed across multiple scaled instances ?

Moreover if we like to deploy the same application using Azure app service as containers (Docker container image), can we run application with the similar capacity size in containers ? What about sticky sessions and scaled instances in containers , is it supported ?

Thanks,
Elango Boopathy.

Answer 1

Hi,

It looks like a P3v2 will be the hardware tier closest to what you're currently using. App Service optionally supports sticky sessions (more info). If possible, you should store the user information in a remote Redis cache. This distributes the session information to all instances. The problem with sticky sessions is that it can cause an uneven distribution of traffic to your instances. Everything I said here applies to deploying containers and/or code.