caching-dotnet-redis-invalidation

What problem does it solve?

When running multiple instances of an ASP.NET Core application, local memory caches on each node can hold stale data after write operations, leading to inconsistent user experiences and data errors across the cluster.

Core Features & Use Cases

• Uses a dedicated Redis instance for cache invalidation pub/sub, with no requirement to share the Redis multiplexer with distributed cache groups.
• Automatically notifies all peer application nodes to clear their local memory cache entries immediately after a write operation, eliminating stale data without manual sync logic.
• Use Case: A scaled e-commerce backend running multiple ASP.NET Core instances can use this skill to ensure all nodes have the latest product inventory data in their local caches after an inventory update, preventing users from seeing out-of-stock items as available.

Quick Start

Use the caching-dotnet-redis-invalidation skill to configure cross-node memory cache synchronization for your multi-instance ASP.NET Core application using Redis pub/sub.