c# - Is the Workflow Foundation Storing State in Memory a Problem? -


We have a contractor who has developed a system that uses the workflow foundation in NAT 3.5. One of my colleagues is worried about "workflow service storage conditions in memory and it is probably getting out of synchronization with our underlying database".
Is his concerns justified?

How is the state stored in memory? WF has persistence service when the example workflow goes into idle condition. You can ensure that the WF is maintained in your database. We do not have any problems. Restarting WF Runtime for creating a specific workflow information - WF to DB Will be raised and executed in the right position.

OK, once again reading you can mean that if you store the state in the workflow (such as the properties of an dependency of an activity) it may be out of sync It depends much more if it is okay or a serialized object created with DB data can be in WF from synchronization, if the original data has changed. If this is a concern, then you want to recreate some objects with DB data and they should not be in the form of a serialized object in their WFF.


Comments

Popular posts from this blog

asp.net - Javascript/DOM Why is does my form not support submit()? -

sockets - Delphi: TTcpServer, connection reset when reading -

javascript - Classic ASP "ExecuteGlobal" statement acting differently on two servers -