Pros
1. Consistent solution for all web sites taking a side-by-side path.
2. Full load balancing can be achieved. Affinity restriction is not applied any more.
3. Can be easily switched to native ASP.NET state management by the end of migration.
4. Better security; data remains on the server side.
5. Does not consume bandwidth; data remains on the server side.
Cons
1. Development cost and time. Custom state management has to be implemented for both ASP and ASP.NET (if third-party software is not acquired).
2. Native state management has to be replaced with a custom one. Minor code changes are necessary.
3. Will become obsolete after all the web sites are migrated.

Table 3: Pros and cons of server-based synchronization.

Back to Article