Should we use a windows service or thread pool?

Question

We are developing a web application in Asp.Net MVC 4, designed for hundreds of users.

We need to have a background service for the user to work with an interval of several minutes.

We are not sure whether to use Windows Services(multiple Windows services) or to use the process thread pool. We think that Windows Services makes them easy to maintain through a Windows server, and this approach can save the overhead of UI programming and thread management. It can also be easily started after a period of time.

Is it possible that it Windows Serviceautomatically initiates a new instance for the new user who has just registered (so we have several instances of background window services, one for each user)? if not the parameter Windows Servicesfalls.

If the upper value is possible, should I choose an Windows Servicesapproach or make my own controlled process of Thread Poolprocesses?

Answer 1

, 1000. , ( ) , . , Windows " ". .

, ASP.NET MVC. , . Windows .

, . . : . HA, .

, Windows Service .

100 , , async IO, 100 .

, . async ( ), . .

Answer 2

:

• , , : - - , ( ), -. , .

• , . , - , , , Windows . ( ), .

• , - . Windows , -.

, ASP.NET , , , - , , IIS. , , ASP.NET, : , , ?

[]

, , .NET, Quartz, , ( - ) , (, , ) .

, , , .NET .

Answer 3

Revalee, . Windows , ASP.NET MVC . .

:

user initiated action
        |
        |           ......................
        |           :  future callback   :
        V           V                    :
======================       ===========================
|   Your web app     |       | Revalee Windows Service |
|                    |       |                         |
======================       ===========================
        |                                ^
        |    registers a callback now    |
        |________________________________|