REST is a widely used architectural style based on the principle of resource orientation. It allows interaction between client and server through standardized HTTP methods. Applications that follow RESTful principles often exhibit high scalability and flexibility.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Representational State Transfer (REST) is an architectural style for networked systems that manipulate resources through representations and a uniform interface.
Roy Fielding coined REST in 2000 in his dissertation on architectural styles for network-based software and derived the style from properties of the World Wide Web.
A client identifies a resource and exchanges its representation through standardized, stateless requests. Hypermedia can reveal the next available action in the current response.
The term captures this component’s central purpose and key decision.
The component connects clear information with a verifiable decision or action.
Application context, responsibilities, limits, and evidence determine practical quality.
REST provides loose coupling for public and internal web interfaces when resources, state, and uniform semantics are modeled clearly. It fits less well for highly stateful real-time interactions; hypermedia and cache semantics must be implemented deliberately.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.