Marc
5/10/2008 4:04:00 PM
A new Asp.Net project is starting up and WF is being considered. An external
end user can create a workflow activity and work on it over a period of a
month. The Old Way is to store user specific data in a db along with state
info and update it as required. Using WF, it appears that the user WorkFlow
is to be persisted to the db and will get hydrated as necessary.
The problem is that there can be serveral hundred users in the system at one
time. The persisting of the WorkFlows will be more db intensive than the
saving user data in the old way.
Also, WF does not have inherent versioning which seem to make it less of an
enterprise ready app.
Am I missing something in this apraisal?
Thanks,
Marc