Can IIS session state be handled by BIG-IP

Hi,

 

 

Many people use BIG-IP to perform the authentication; but full session state management is typically something done on the web servers using either system memory or on a database.

 

 

BIG-IP persistence functionality ensures that clients are directed to the same web server over multiple requests. The underlying reason to persist a client is to make sure the client is sent to the web server that has their session information. This allows you to load balance multiple web servers without a requirement for the web servers to share state information with each other.

 

 

What kind of state management are you currently doing on the web servers? What are you considering offloading to the BIG-IP?

 

 

Assuming you're able to ensure that clients are persisted to the same web server they created the session with, is there any reason you would want/need to offload the state information to the BIG-IP?

 

 

Aaron