Because each back-end system is running in a separate process, any integration architecture is
required to cross multiple process boundaries. A Service-Oriented Integration (SOI) architecture
also introduces SOA Services that run in their own process, thus adding more process boundaries
to be crossed. What approaches can be employed to reduce the performance impact of crossing
multiple process boundaries?
A.
There is nothing that can be done because process boundaries are just part of any integration
architecture.
B.
The SOA Services should expose larger-granularity operations to reduce the number of s-calls,
which reduces the number of times process boundaries are crossed.
C.
Service composition should be used to reduce the number of SOA Services that are exposed to
the clients
D.
The SOA Services should use XML-based request-and-response messages because XML is a
platform- (and hence process-) neutral format.
E.
The SOA Services can encapsulate multiple layers of theSOI architecture to reducenumber of
service calls, which reduces the number of process boundaries being crossed.
Explanation:
Each time a process boundary is crossed there are performance impacts from the
network and message marshalling and de-marshalling. This is a primary reason why
SOA Services should expose relatively course-grained interfaces (B).
This is also a reason why a service implementation might span multiple layers in the architecture
.(E)
Reference: Oracle Reference Architecture, Service-Oriented Integration, Release 3.0, Process
Boundaries