Upcoming changes to ManualWorkflowScheduler post beta 2.2

Dear Matt,

Hope you are doing fine.

I’ve one query regarding performance in the following scenario …

User is creating a Ticket from asp.Net page which may or may not be sent for approval before processing. In each case the WF will be called to persist its state. The Admin user can view/process the ticket, or can send for approval if required. Whenever the ticket is created, I want to invoke the workFlow runtime to save the state of the ticket and when the Admin user logs , I again want to get the ticket from its latest state using the WorkFlow Runtime.
Now ,

1) If suppose 1000-2000 users are accessing the Site to create/view their tickets then how many WorkFlow runtime Instances will be created ?

2) Will it affect the performance of the site?

3) If there is only one instance is created the how can we get the correct ticket ?

4) Which is the best way to use workFlow here ( Exposing WF as a windows service or calling WF runtime directly from Asp.net page everytime ?)

It would be great if you can suggest me the hosting and calling WF in this scenario.


Best Regards,
Dharmesh

Dharmesh,
See my response to your query in the WF forums