serverpod-caching

Reduce redundant Serverpod database queries by storing frequently accessed data in session.caches. Use local in-memory storage for session-level caching or Redis-backed global caching to avoid repeated reads.

A CacheMissHandler automatically computes and stores values only when a cache lookup fails. Configured with an explicit lifetime, it populates the cache on demand without manual get-put logic.

Invalidate related Serverpod cache entries by assigning them to cache groups. Grouping coordinated entries allows targeted invalidation patterns to clear stale data across related keys when underlying values change.

You can cache both serializable custom models and supported primitives in Serverpod session caches. Typed get and put APIs ensure strongly typed reads for retrieving stored values.

Structure Serverpod cache keys using stable, deterministic formats like EntityName-id. Well-formed keys prevent collisions and ensure accurate data retrieval across request and real-time workflows.

Use local in-memory caching for session-specific data within a single instance, and Redis global caching for shared data across multiple Serverpod instances. Both require explicit lifetime configuration to manage expiration.