Passivation
Long running workflows spend more time waiting for something to happen than actually executing. Keeping the workflow in memory consumes resources that could be used by other workflows or programs running on that machine. In addition, it might be necessary to bring the machine down for maintenance. And of course, servers never crash.
Under these circumstances it becomes necessary to save, and then restore the state of the workflow. This is called passivation. In addition, one can passivate a workflow because one wants to create a save point to which the workflow can be restored.
As we have previously seen, the workflow is nothing but a data structure. Hence, it can be serialized as part of the passivation process by using a persistence ...
Get Building Applications with Windows Workflow Foundation (WF): Advanced Workflow Features now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
