wcfworkflow-foundation-4workflowservice

Workflow Service vs WCF service that executes a single workflow


Trying to decide if I need to implement a WF service or just stick with a WCF service that simply invokes a workflow and returns the result.
I dont need correlation handles, or any need to pause the workflow somewhere in the middle of its execution. It just merely needs to execute a workflow and return the result. Also, I might want to add a few methods to the service that do not involve workflows at all. So is there benefit one way or the other, or is a WF service just a pretty wrapper for exposing a workflow as a service?


Solution

  • I would recommend that you do not go for WF service if you don't need the bells and whistles. The WF Service really puts you into an enterprise-oriented use case straitjacket. If that's not where you're going then go for a looser integration with WF.

    My two cents.