So, about this WF thing....
-
Ok, I've started reading up on WF 4.0... And I keep coming back to a philosophy question. If I were to put a workflow together to move data around... Would you write the work flow against an individual record? Or would you write the workflows against the set. Let's take a simple console app: I have a bunch of records That I extract from the SQL tables, work on them via a web service, receive a response, and update the sql table with a response code. One could write it like this: Harvest all available records to my staging table. Foreach: Select a record Call the web service Update the record back in the database End Foreach Stop. Or possibly write them as 3 steps. Harvest Post Update and each of the 3 would be a separate activity. The first is more of a workflow acting on a single record and sending the record to the workflow, the 2nd is more along the lines of simple 3 activity workflow. So what do you all think?
This are my own opinions. You know the rest.....
-
Ok, I've started reading up on WF 4.0... And I keep coming back to a philosophy question. If I were to put a workflow together to move data around... Would you write the work flow against an individual record? Or would you write the workflows against the set. Let's take a simple console app: I have a bunch of records That I extract from the SQL tables, work on them via a web service, receive a response, and update the sql table with a response code. One could write it like this: Harvest all available records to my staging table. Foreach: Select a record Call the web service Update the record back in the database End Foreach Stop. Or possibly write them as 3 steps. Harvest Post Update and each of the 3 would be a separate activity. The first is more of a workflow acting on a single record and sending the record to the workflow, the 2nd is more along the lines of simple 3 activity workflow. So what do you all think?
This are my own opinions. You know the rest.....