Last post Dec 20, 2011 01:32 AM by mitja.GTI
Dec 20, 2011 12:44 AM|Sulaiman.Tanveer|LINK
I need help in designing the app we are creating, where either windows service is required or an app that is running continuously and communicate objects with asp.net clients and keeps the state of the objects
what this app is intend to do is it has different users, and behind it there is a manager/handler who knows what that particular user has to do,what are the statuses of each work assigned are,and real-time status monitoring and ensure that this work is not
assigned to any one else.
Since the expected load of the application will be more then 10,000 ppl we want this application to be robust.
please share with me how this can be done, what technologies should be used and design patterns.
Dec 20, 2011 01:32 AM|mitja.GTI|LINK
for me, this is not enough data to suggest you the best solution, but this might help you:
Asp.net has a default setting of shutting down after 20 minutes of idle time. If you need your application to constantly run (you were mentioning real time status monitoring) then i suggest you create a WCF hosted by Windows Service.
But if this is going to be just a web page then you can go either with asp.net or MVC. Just make sure you use caching and follow best practices for developing fast web sites (YSlow - Yahoo).