liveBook · Manning

Cacheability

As explained in Grokking Software Architecture

Cacheability is the property that a response can be stored and reused for equivalent subsequent requests according to explicit freshness and validity rules.

Cacheability means a response explicitly says whether it can be saved and reused. In REST, this constraint helps reduce network traffic and supports the web’s resilience and scalability. section 6.9.1 section 6.9.5

A vending-machine response

A REST request for a product returns the whole product response, even if you only wanted its name. That response is simple and highly cacheable, but may include data you do not need. section 6.4.1

How Grokking Software Architecture covers it

How deep it goes
Defines the response-level reuse constraint and its benefit, without detailing freshness rules or cache configuration.
Examples
Uses a product response to show how simple, cacheable retrieval can over-fetch data.
What you can do after
Understand why REST uses cacheable responses and recognize the tradeoff with over-fetching.
How it connects
Connects cacheability to REST, statelessness, uniform interfaces, and scalability.

Also explained in

Compare how 3 books explain cacheability →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Grokking Software Architecture. The section links point to the parts of the book it draws on.