Workflow in production code

Question

Hi, I would like to know how many of you have used Workflow in your work environment and was this a good idea? I mean, we can create the same thing using the DB service and scheduler

Answer 1

We use WF in our production environment. We have 6 different workflows that you can start. They are divided into 3 statemachine and 3 sequences. In some cases I will use it again, but in others I would not. I would like to argue that part of the statemachine workflow was copied at the end quickly, I'm not sure that this is the main part of the workflow throughout the design.

I would use the workflow again for short running processes, such as quotation marks or transformations of things, before sending them this way.

statemachine - , WF, . , (, ).

: (, 8000 ). , WCF (.NET 3.5) - , , .

, : , , statemachine.

. , : Windows Workflow Foundation ?

Answer 2

Sharepoint, WF . . , WF , .

, ? WF .NET 3.0+ , .

Answer 3

Most people talk about good things in Workflow, but I noticed that they introduce unnecessary code complexity and maintenance problems. They are suitable for a certain class of problems. others then that they need a lot of code plumbing and repair nightmares.