liveBook · Manning

Cacheability

Cacheability is the property determining whether a response or resource representation may be stored and reused for equivalent subsequent requests under freshness and validity rules.

How 2 Manning books explain it

Building Web APIs with ASP.NET Core

Cacheability is the REST constraint that specifies whether and for how long a response may be reused from a cache.

How it is used
Uses response labels to permit safe reuse, reduce client work, and support web API performance and scalability.
How deep it goes
Defines response reuse and demonstrates attribute settings, stopping at HTTP headers rather than detailing cache internals.
Examples
Shows [ResponseCache] configured with a 60-second duration for cacheable responses and NoStore for noncacheable responses.
What you can do after
Apply it via ASP.NET Core [ResponseCache] to label controller responses cacheable or noncacheable.

Read how Building Web APIs with ASP.NET Core explains cacheability →

Acing the CCNA Exam: Volume 2 Advanced Networking and Security

Cacheability is the property that determines whether a resource representation may be temporarily stored and reused.

How it is used
Uses cacheability as a REST constraint for deciding whether resource representations can be stored and reused.
How deep it goes
Defines temporary reuse, efficiency benefits, marking requirements, and freshness and security limitations without implementation details.
Examples
Uses repeated resource retrieval, frequently updated information, and sensitive information as caching scenarios.
What you can do after
Evaluate whether REST resources should be cached and recognize freshness and security risks.

Read how Acing the CCNA Exam: Volume 2 Advanced Networking and Security explains cacheability →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.