Question

A company runs a stateful ASP.NET web application across a horizontally scaled Azure App Service plan with 8 instances behind a load balancer. Users report being unexpectedly logged out and losing shopping cart contents when their requests hit different instances. The architects want a solution that externalizes session state so any instance can serve any request, provides sub-millisecond read latency, and scales independently of the web tier without requiring code that pins users to a single instance. Which approach should they recommend?

Accepted Answer

Store session state in Azure Cache for Redis and configure the application's session provider to use the distributed cache.

Answer

Enable Application Request Routing (ARR) affinity (sticky sessions) on the App Service so each user is consistently routed to the same instance.

Answer

Persist session state to a shared Azure SQL Database table read and written on each request.

Answer

Store session objects in Azure Blob Storage and load them at the start of each request.