Representational State Transfer (REST)

Go up to Terms and Definitions

Discussion

Representational State Transfer (REST) is an implementation interface style that exposes resources through a uniform set of operations and resource identifiers.

A REST interface typically uses resource-oriented interaction, request and response messages, representations of resource state, stateless interaction, and standard protocol mechanisms. In common web implementations, REST interfaces often use HTTP methods, URIs, headers, status codes, and payload representations such as JSON or XML.

In the FX Demo Reference Architecture, REST references identify possible implementation mechanisms. REST does not define the logical meaning of a Communication Endpoint, Node, data structure, policy decision, release package, or runtime plane.

A REST interface can realise, expose, or support a logical communication pattern selected by an implementation profile. The logical architecture remains independent of REST resource design, URI design, HTTP method selection, payload format, authentication mechanism, deployment boundary, and service implementation.

Definition

implementation interface style that exposes resources through a uniform set of operations and resource identifiers

Source

Generalised from common software architecture usage and specialised for use in the FX Demo Reference Architecture.

Note

REST is not a logical Communication Endpoint, Application Programming Interface (API), data structure, message, runtime plane, deployment artefact, or policy mechanism. A REST API may implement or expose an architectural interaction selected by an implementation profile.

Example

A later implementation profile may expose an FX Release Package through a REST resource, while the logical architecture defines the release interaction through the FX Release Package Endpoint.