Loosely Coupled Design – Help (Contract First Questions)

Home Page › Forums › BizTalk 2004 – BizTalk 2010 › Loosely Coupled Design – Help (Contract First Questions)

Viewing 1 reply thread
  • Author
    Posts
    • #19959

      Hi everyone,

      i’m hoping to have some debate on this from anyone who is interested. I think there is a flaw in my knowledge/understanding… I could use some help.

      When designing/building and SOA, we ought to follow a loosely coupled design paradigm, which is helped if we follow a contract first approach. Great.

      Background

      In the .NET world, we have WCF to help facilitate. I am assuming all of the following is done with WCF. I see there being 2 different approachs, and I can’t quite figure out the best appraoch when designing an SOA…

      1) Messaging Only / Doc Literal. E.g. (message in italics)

      <soap>

        <header>…</header>

        <body>

          <person>

            <name>Me</name>

          </person>

        </body>

      </soap>

       

      2) RPC or Pseudo RPC. E.g. (wrapper in bold)

      <soap>

        <header>…</header>

        <body>

          <someMethod>

            <person>

              <name>Me</name>

            </person>

          </someMethod>

        </body>

      </soap>

      The Issue

      Now, from what I can tell, it is impossible to do 1) using BizTalk + WCF. It is not possible using the WCF publishing wizard (schema or orchestration) to post XML fragments into BizTalk without the RPC style method wrapper. Do I need the HTTP adapter? If so, I loose access to nice things like WS-Security.. etc

      The Problem

      In developing a loosely coupled design following a contract first approach, I feel the RPC style formatting dirties the contract and imposes coupling. Imagine an ESB style scenario, the service to process the message should be documented within the header. The service will recieve the XML fragment and process it, it does not need the RPC style wrapper.

      So, how do you guys do this stuff in your environments? Do you have contract and schema repositories that use common schemas to express data, but send information RPC style. Or do you use ESB style loose coupling and just post XML fragments into BizTalk for processing and routing?

      Thanks all

      TM

    • #19961

      I have been using the RPC style approach.  You’re right, the WCF publishing wizard doesn’t allow you use a message only approach.  That said, I bet there is a way that you can take the service that the wizard generates and modify it to accept only the message without any wrapper.

Viewing 1 reply thread
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.