liveBook · Manning

Distributed caching

Distributed caching is a technique for storing reusable data in a cache shared across multiple networked processes, servers, or nodes.

How 4 Manning books explain it

Building Web APIs with ASP.NET Core

Distributed caching is a caching technique that stores reusable data in shared storage so multiple application instances can access it.

How it is used
Reduces repeated database work in a web API while sharing cached entries across application servers.
How deep it goes
Walks through SQL Server setup, cache helpers, controller use, and Redis substitution; leaves other SQL provider options unexplained.
Examples
Uses a cached, paginated mechanics GET request, SQL Server cache-table configuration, Redis registration, and a table-renaming exercise.
What you can do after
Apply it via IDistributedCache with a SQL Server or Redis provider to cache API query results across servers.

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

Pro ASP.NET Core 7, Tenth Edition

Distributed caching is the technique of storing cache data in a cache shared by multiple application instances or servers.

How it is used
Uses a shared SQL Server cache for application data and a distributed-cache element for rendered content across application servers.
How deep it goes
Walks through database, table, package, connection-string, and service setup; describes content-tag behavior without a distributed-content test.
Examples
Shows a SQL cache table and Program.cs registration, then contrasts cached and uncached Razor timestamps on page reload.
What you can do after
Operate/configure it by backing an ASP.NET Core cache with SQL Server and selecting distributed-cache for shared rendered content.

Read how Pro ASP.NET Core 7, Tenth Edition explains distributed caching →

Advanced Algorithms and Data Structures

A distributed cache is a cache partitioned across multiple processes or nodes that coordinate request routing and data storage.

How it is used
Scales caching across processes or nodes when one cache cannot hold or serve the required workload.
How deep it goes
Explains nodes, routing, consistent hashing, and limited remapping, but stops short of cache implementation details.
Examples
Uses database results, billion social-media walls, high request rates, and a consistent-hashing node-ring figure.
What you can do after
Evaluate distributed-cache layouts and understand how consistent hashing limits reassignment during node changes.

Read how Advanced Algorithms and Data Structures explains distributed caching →

Building Distributed Applications that Work

Distributed caching stores frequently accessed data in a shared cache accessible across multiple servers or nodes.

How it is used
Improves application performance and scalability by sharing frequently accessed data across servers or nodes.
How deep it goes
Defines the shared-cache mechanism and explains RAM-based speed and cross-application access, without implementation steps.
Examples
Uses Redis and illustrates applications sharing data populated by another application.
What you can do after
Understand how applications can reuse data from a shared cache to improve performance.

Read how Building Distributed Applications that Work explains distributed caching →

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.