Finding the Compromise – the Adapter Framework - Applied SOA Patterns on the Oracle Platform - page 363

handle it through the application of the Protocol Bridging SOA Pattern. That's the classic
integration approach with transformation service agents in the ABCS framework. By the
way, please note that the Concurrent Contract is always based on the application of the
Service Facade. Also, just for the sake of SOA exam preparation (S.90.xx), keep in mind
that Facade in SOA terms is something present inside the Service.
What if you have the HTTP as your solid Canonical Protocol for transport, but your mes-
saging protocols can be SOAP over HTTP, plain HTTP(s), and HTTP REST-style? Yes,
that's quite a common situation when some clients would like to have unified protocol op-
erations ( POST , GET , PUT , DELETE ), and others prefer more meaningful operations, ex-
pressed in WSDL.
That's a really interesting issue; please see the following figure:
Why would you need that? For example, in the context of telecommunication primes
which we discussed in Chapter 3 , Building the Core - Enterprise Business Flows , we are
quite aware of the common trends in current video entertainment options, which are listed
as follows:
• Video on Demand ( VoD ) and classic Linear TV should not be seen as separate
delivery channels, but presented as a combined media resource with consolidated
assets for live (or near-live) programs and on-demand sources. These assets