Workflow Manager 1.0 in N-Tier architecture RRS feed

  • Question

  • WF Manager exposes Workflow applications as REST Services and provides other management tools such as ESB etc.

    In order to adopt WF Manager in N-Tier architecture where SOA drives the development, below architecture is identified.

    Sharing your expertise is greatly appreciated.

    • Client invokes the Web API service based on WF REST service workflow outcome.
    • WF Manager is responsible for only Workflow application - stand alone.
      When the WF service fails, the other service that is responsible to provide data still available.

    In summary it follows separation of concern.

    Example:- Approve workflow. Object state 

    1. Client query WF service to obtain 'object state (State machine workflow)'
    2. Based on the service response with object state client invokes the Web API service to interact with underlying database
    3. Business logic is in client application that interact with both services(WF and Web API REST Services)

    Best regards

    Apriori algorithm [association rule]

    • Edited by Raju Golla Wednesday, July 3, 2013 9:29 PM
    Wednesday, July 3, 2013 2:58 PM