Windows Azure Addressing Instances and Sticky Sessions

To prove the conceptual work, I gathered facts about Windows Azure. There are 2 topics left for which I could not find a final answer.

  • Sticky sessions / sticky load balancing are not possible, am I right? Maybe there is an opportunity using Azure Traffic Manager (WATM)?

  • Can individual deployment instances be addressed or are they all behind this opaque Azure wall? Or at least can an instance at runtime determine its own identifier or something similar to write to the log?

+5
source share
3 answers

Find the answers below:

  • / , ? , Azure (WATM)?

. Windows Azure. , Traffic Manager, . , . , . .

2. , Azure? , , - ?

. Windows Azure FireWall. , , . CurrentRoleInstance RoleEnvironment. RoleInstance, ID.

+1

astaykov, , .

- . (, Web Worker, , sharptooth, ), .

, ( ip: ), .

msdn.

+1

, :

  • State server. This will allow you to receive encrypted data from server to server even outside your network. You can do this by implementing State Server for each instance of your web applications or servers.

  • SQL Server (in memory, this is only available in versions 2014 and later)

  • Redis cache on azure

Three options handled almost any session problem that I encountered in the last three years.

0
source

All Articles