a bit new for the Windows workflow, so easy :)
I want to create a host working environment that has high availability - at least 2 WF runtime hosts on separate hardware that point to the same persistence or track the SQL database.
I am looking for a template in which I can asynchronously create new workflow instances based on some external event (i.e. some parts of the data are updated in the database by another application). For each event, I need to create exactly one instance of the workflow and it does not matter on which host this instance is created. There is also flexibility regarding the length of time between the event and the actual instantiation of the workflow.
One of the solutions that I am considering is the WCF interface on the WF hosts and placing them behind some kind of load balancer. Then there will be some part of the system that fires an “event” to make a WCF call.
I am not very happy with this, because if both \ WF hosts are omitted or inaccessible, the event may be "lost". In addition, I will not be able to manage the download as I would like. I suppose a situation where there can be many events in a short period of time, but it is quite acceptable to handle these events after a while.
So, I believe that I need to somehow persist in the events and separate the creation of the event from the processing of events.
MSMQ SQL Server, WF- ? , ...
NServiceBus ?
.
. . WF , , SQL. , :)
MSDN WF
, WF , . , , .
user1010