Best Practice for State Management in a Distributed ASP.NET MVC 4 Application -
i building enterprise application asp.net mvc 4, following n-tier architecture (including web farm load balancing , possibly application farm). best practice manage state such distributed architecture?
i know can go sql state management, choice keeping performance in mind (especially considering many inter-server calls)? other options have if not want use session
variables @ (due performance issues or don't want handle session timeouts)? how using @html.serialize()
?
apologies if similar question has been asked before, search did not result in definitive answer.
edit: here of key metrics: volume of users - 1.2 millions concurrency - during peak time, transactions high 800 per minute geographic diversity - , europe caching - there plan use distributed caching (appfabric) availability - 99.99%. internet site 1 of largest retailers in world , expect high growth rate.
Comments
Post a Comment