The Service-Oriented Integration (SOI) architecture includes an event-handling capability as
illustrated and described in the Process View. Which statement best describes the rationale for
including event handling in the SOI architecture?
A.
Event-Driven Architecture (EDA) is a subset of SOI, so including event handling provides the
EDA part of SOI.
B.
The event-handling capability allows arbitrarily complex events to be handled by the
architecture; i.e. Complex Event Handling (CEP) is part of the SOI architecture.
C.
AH other interactions within the architecture are upper layers calling lower layers. The eventhandling capability allows a Connectivity Service to call a Business Service, thus providing the
ability to lower layers to call upper layers in the architecture.
D.
The event-handling capability allows a back-end system that is included in the SOI to initiate
action because something important has occurred within the back-end system.
E.
By employing a publish-and-subscriber message approach, the event-handling capacity allows
the SOI architecture to handle high-volume message traffic because publish-and-subscribe
handles higher message volumes than request-response.
Explanation:
Note:
Events allow one system (event emitter) to notify other systems (event sink) that
something of interest has changed. There are two broad categories of event types:
* Business Event – A business event is an event that is of business relevance and
would be readily understood by a business person.
* Technical Event – A technical event is an event that is relevant to IT but not
directly relevant to the business.
As illustrated by the figure below, in this architecture all events are routed to the Business
Process Layer and the appropriate business processes are executed for that event.
Essentially this is a mechanism for a lower level in the architecture stack, the
Connectivity Layer, to initiate actions that might include interactions with all other
levels in the architecture. This is essential since the generated event will likely be
backend system specific; therefore it is likely that the data must be normalized and
some amount of custom logic may be required to convert the event into an event that
is backend system agnostic.Reference: Oracle Reference Architecture, Service-Oriented Integration, Release 3.0
