Subject: Re: [regrep] Direct Data Exchange vs. SOA
Yes - excellent point. I'm also thinking that in (2), we have some shared services accessible as business components (which are represented as services), vs. all trading partners having their own business logic in (1), which may be duplicated among business partners (a good reason to use SOA). For example, let's say we have a purchase order/invoice exchange, and one particular field of the purchase order (one XML element) is calculated based on X other fields (elements). In (1), each PO sender would have to calculate that field in their own system and populate it, whereas in (2) they could leave it blank and allow the shared service to calculate/populate prior to sending it to the recipient, based on a shared computation accessible from a service. Joe "Monica J. Martin" wrote: > > >>>Chiusano: I hope to get some good insight in response please: > >>> > >>>Let's say we have a purchase order process between trading partners (PO > >>>sent, Invoice received). There are (for the purposes of this inquiry) 2 > >>>possible ways to handle this process: > >>> > >>>(1) Direct Data Exchange (create XML documents based on a common schema, > >>>and exchange them between trading partners) > >>> > >>>(2) SOA (have a purchase order/invoice shared service that is discovered > >>>in a registry, etc.) > >>> > >>>My inquiry is: What would drive an organization to use one approach or > >>>the other, from both a business and technical standpoint? For instance, > >>>would "critical mass of services and/or trading partners" be a driver > >>>for SOA vs. direct data exchange? > >>> > In the discussion, suggest we also recognize and account for the fact > that in (1) and (2) that the business process definition may guide the > exchange regardless of if via a service or via the document exchange. > Thanks.