Additional SOA Patterns –Supporting Composition Controllers - Applied SOA Patterns on the Oracle Platform - page 588

• TaskProcessor is the actual worker that executes the task. TaskPro-
cessor is assigned according to TaskDispatchPolicies , which could be
simple Round-robin or Attribute Matching. The last type is purely content-based
routing/mediation.
• The submission's result is returned to the SubmissionResult cache.
Although very schematic, this sequence is quite complete to recognize the resemblance
with patterns we implemented using SOA Suite in Chapter 3 , Building the Core - Enter-
prise Business Flows ; please see the figure with the block diagram for Composition Con-
troller with Business Delegate and Service Locator. Exactly as with Service Broker / Busi-
ness Delegate patterns, follow the ensuing steps:
1. First of all, we decouple the consumer and actual worker.
2. We use the dynamic execution capability (here in Java).
3. We can postpone the execution until a certain event has occurred.
4. We can route our object conditionally or unconditionally to the predefined
TaskProcessor (Service) and we use an external policy for the Task-Process
association.
Coherence empowers these patterns with the highest resiliency and top processing speed.
Its distribution model is based on event mappings and notifications, and it fully supports
multithreading. All of this makes it a perfect companion for Oracle EPN.
Here, we would like to discuss two most common types of Coherence implementations,
and we will traditionally start with the classic OSB and Coherence integration.