Architectural Styles and the Design of Network-based Software Architectures¶
Fielding, R. T. (2000). Architectural Styles and the Design of Network-based Software Architectures.
Cited by¶
5 citations across 5 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Adjacency Pair
- Network protocols and API design. Request/response with explicit timeout, NACK signalling, and retry policy; the timeout is the operational instantiation of noticeable absence, and repair appears as retry-with-backoff and idempotency keys.
This sourceDefines the REST request/response model with typed response classes (2xx/3xx/4xx/5xx); supports request/response as an engineered adjacency pair with timeout and retry as repair.
- Network protocols and API design. Request/response with explicit timeout, NACK signalling, and retry policy; the timeout is the operational instantiation of noticeable absence, and repair appears as retry-with-backoff and idempotency keys.
- Idempotence
- Without all six parts the property is undefined and the safety argument fails; with them, the spectrum from a projection operator in linear algebra to a Stripe payment-intent retry to a Kubernetes reconciliation loop is analyzed within one diagnostic vocabulary, and the question "is it safe to retry?" becomes a checkable engineering question rather than an ambient hope, as Fielding's (2000) REST architectural style first codified for HTTP methods.
This source(Establishes REST API idempotence contract as design principle; `PUT`, `DELETE` idempotent, `POST` non-idempotent.)
- Without all six parts the property is undefined and the safety argument fails; with them, the spectrum from a projection operator in linear algebra to a Stripe payment-intent retry to a Kubernetes reconciliation loop is analyzed within one diagnostic vocabulary, and the question "is it safe to retry?" becomes a checkable engineering question rather than an ambient hope, as Fielding's (2000) REST architectural style first codified for HTTP methods.
- Interoperability
- Permeability
- A well-designed boundary is selectively permeable — it exposes the intended call (throttled by rate limits, an amount-selective control) while sealing internal state.
This sourceFoundational account of REST and service-boundary design — selective exposure of endpoints and concealment of internal state.
- A well-designed boundary is selectively permeable — it exposes the intended call (throttled by rate limits, an amount-selective control) while sealing internal state.
Domain-specific¶
- Request-Response
- REST builds a resource-oriented application layer on top of this exchange primitive.
This sourceThe dissertation defining REST, deriving it by layering resource identification and uniform-interface constraints onto a client-server request-response exchange.
- REST builds a resource-oriented application layer on top of this exchange primitive.
Verification¶
This reference passed the adversarial substantiation pipeline: it was checked to exist and to support the claim it is attached to. See how references were verified.
Registry ID ref:619f36c25a9e · see in the full table