Caching is a great way to improve the latency an application. Traditionally, when you implement caching, you need to play with the API of the caching framework (such as MemoryCache) or caching server (such as Redis) and to include moderately complex logic to your source code to generate the cache key, check the existence of the item in the cache, and add the item into the cache. Another source of complexity stems from removing items from the cache when the source data is updated. Implementing caching manually is not only time-consuming, but also is error-prone: it is easy to generate inconsistent cache keys between read and update methods.
PostSharp allows you to dramatically reduce the complexity of caching. It allows you to cache the return value of a method as a function of its arguments with just a custom attribute, namely the CacheAttribute aspect. The InvalidateCacheAttribute aspect and the CachingServices.Invalidation API offer a strongly-typed way to invalidate cached methods. Additionally, PostSharp is independent from the caching framework or server (called caching backend), so you can choose from several backends or implement an adapter for your own backend.
This article shows how to make method returned values being cached.
This article shows how to prevent PostSharp from logging cache hits, which has a performance impact.
This article shows how to invalidate cached returned values of methods declaratively and imperatively.
This article shows how to invalidate cache items automatically using cache dependencies.
This article shows how to customize the cache keys which identify cached method return values.
This article shows how to store cached values in various backends.
This article shows how to invalidate all related in-memory caches in a distributed environment.
This article explains how you can prevent the same method from being executed with the same arguments at the same time - by using locking.