Requester Role

Return to R Terms

Discussion

A Requester Role identifies a Logical Node's responsibility for initiating an information exchange that expects a response.

The Requester Role supports request/response interactions without prescribing REST, RPC, service calls, synchronous messaging, or any other specific mechanism. The Logical Architecture identifies the request endpoint, the response expectation, the information structures involved, the Runtime Plane, and the traceability expectations.

A Logical Node performing a Requester Role produces a logical request and expects a logical response or outcome from a Responder Role.

Definition

Communication Role responsible for initiating an exchange that expects a response.

Source

Specialisation of Communication Endpoint and Node Role from Part 1, Sections 7.6 and 7.4; generalised from request/response, control, policy, and service-interaction material in the original FX Demo Reference Architecture.

Note

A Requester Role does not require REST, RPC, blocking calls, or direct service invocation.

Example

A logical Release Control Node performs a Requester Role when it requests a policy decision from a logical Policy Evaluation Node.

Return to Top