|
|
09-27-2007
Registered User
26,240,
27
Prepare for a Lively SOA ?Request-Reply? Debate
Tim Bass
Thu, 27 Sep 2007 22:34:57 +0000
It looks like the event processing blogosphere is about to be energized with a lively discussion.**** Opher has opined that SOA is not inherently request-reply.*** Pen to paper!** Let the lively debates begin!
Kindly turn your attention to IBM’s discussion of SOA and their figure below.
The IBM*figure was derived from the original W3.org view of SOA, Register-Find-Bind,* found here*in a figure titled “SOA”.
Kindly notice that Bind, as defined by W3.org has a two-way arrow.** This is a request-reply architecture.
In addition, IBM*(from the link referenced above)*also defines these properties of an SOA:
CapabilityDescriptionLoosely coupled interactionsServices are invoked independently of their technology and locationOne-to-one communicationsOne specific service is invoked by one consumer at a time. The communications are bidirectionalConsumer-based triggerThe flow of control is initiated by the client (the service consumer)SynchronousReplies are sent back to the consumer in a synchronous wayEOP
Source...
Thu, 27 Sep 2007 22:34:57 +0000
It looks like the event processing blogosphere is about to be energized with a lively discussion.**** Opher has opined that SOA is not inherently request-reply.*** Pen to paper!** Let the lively debates begin!
Kindly turn your attention to IBM’s discussion of SOA and their figure below.
Kindly notice that Bind, as defined by W3.org has a two-way arrow.** This is a request-reply architecture.
In addition, IBM*(from the link referenced above)*also defines these properties of an SOA:
CapabilityDescriptionLoosely coupled interactionsServices are invoked independently of their technology and locationOne-to-one communicationsOne specific service is invoked by one consumer at a time. The communications are bidirectionalConsumer-based triggerThe flow of control is initiated by the client (the service consumer)SynchronousReplies are sent back to the consumer in a synchronous wayEOP
Source...