Have Geek Brain

Change paradigm to use WorkFlow

Have you thought about the advantages / disadvantages of using WorkFlow in a new development? It looks like it will change the paradigm a bit, wondering if it is worth the effort.

0


a source to share


3 answers


Before diving into WF, be sure to analyze the workflows you want to implement. If they are fairly simple and / or short-lived, I would think twice.

My experience is that it pays off when workflows can live for long periods of time (hours / days / weeks), especially when combined with a persistence service. In the project I used it on, we realized that out of the two main workflows we have, one of them will probably work just as well without using WF.



Another (which is mailing information that is sent via SMPT and then waits for one of several predefined responses in the mailbox and resends the message at regular intervals if no response arrives). I think this is a good case for WF.

+1


a source


Don't use Workflow on desktop apps. Due to its multithreaded design (which is ideal for servers, especially web servers), latency is quite high between state transitions.



+1


a source


If this doesn't sound like a natural fit for your project, you probably won't need it.

0


a source






More articles:


All Articles