Reliable Messaging

Asynchronous Queuing

Intermediate Routing

Policy Centralization

The application of the Intermediate Routing pattern is suitable for handling message routing requirements that are dynamic in nature and difficult to anticipate in advance.

The application of the Intermediate Routing pattern is suitable for handling pre-determined message paths with fixed routing requirements that cannot be changed at runtime.

The application of the Intermediate Routing pattern tends to improve runtime performance when compared to an approach whereby routing logic is embedded within individual services.

None of these statements are true.

The need to increase the autonomy of a service due to its reliance on a shared data source.

The need to perform content-based routing based upon metadata found in the message header.

The need for load-balanced access to a redundantly deployed service.

The need to provide pre-defined compensating logic for when an atomic service transaction fails.

Atomic Service Transaction

Intermediate Routing

Service Broker

Decoupled Contract

common routing logic being removed from service logic and placed into service agents

common routing logic being removed from service agents and placed into a database

common routing logic being physically centralized into a single service

common routing logic being physically centralized into a single service composition