RoundRobin

If the target operation group type for the SG1 target operation group is defined as RoundRobin, the Core Engine uses the RoundRobin routing algorithm. For the RoundRobin routing algorithm type, the Core Engine selects the target operation in a RoundRobin fashion. This means that the Core Engine rotates through the list of target operations one at a time to process the client requests.

Figure RoundRobin Routing illustrates the SG1 target operation group with RoundRobin type.

When the Core Engine routes the client requests to SG1 target operation group, the target operation from the SG1 target operation group is selected as follows to process the client request:

  • The first facade request Request 1 is forwarded to target operation A.
  • The second facade request Request 2 is forwarded to target operation B.
  • The third facade request Request 3 is forwarded to target operation C.
  • The fourth request Request 4 is forwarded to target operation A. The subsequent facade requests are forwarded to target operation B, then target operation C, and so on.

Scheduling Pattern

The Core Engine uses the following scheduling pattern for the RoundRobin algorithm type:

(Target Operation A, Target Operation B, Target Operation C, Target Operation A, Target Operation B, Target Operation C, Target Operation A, and so on.)

If the selected target operation is not running or times out to process the facade request, the Core Engine processes the request as follows:

  • Retries to route the request to the same target operation as per the retry mechanism.
  • The Core Engine does not route the facade request to an alternate target operation in the target operation group.
  • Returns the fault message to the client for the facade request.
    RoundRobin Routing