First and foremost, the CacheRepository is NOT web specific!
The CacheRepository library contains the abstract CacheRepositoryBase class, which can be implemented by any caching system that you choose. The CacheRepository.Web NuGet package includes a WebCacheRepository implementation that leverages System.Web.Caching.Cache
Get all of the source code, unit tests, and a complete MVC4 sample application (preconfigured to include dependency injection with Unity) from GitHub. Or to just jump in and start using it, grab the CacheRepository.Web package from NuGet.
ICacheRepository
The ICacheRepository interface has all the standard Get, Set, Remove and Clear methods. Additionally, these methods have been expanded to include enum parameters to group manage cache expiration.
Best of all, it includes GetOrSet methods. These methods will try to get the value of the specified key, and when it can not find that value it will then be loaded via the passed in Func. A key feature here is the fact that the setter of the GetOrSet will lock on load to prevent redundant data loads. (More details about this below.)
public interface ICacheRepository
{
object Get(string key);
T Get<T>(string key);
T GetOrSet<T>(string key, Func<T> loader);
T GetOrSet<T>(string key, Func<T> loader, DateTime expiration);
T GetOrSet<T>(string key, Func<T> loader, TimeSpan sliding);
T GetOrSet<T>(string key, Func<T> loader, CacheExpiration expiration);
T GetOrSet<T>(string key, Func<T> loader, CacheSliding sliding);
void Set<T>(string key, T value);
void Set<T>(string key, T value, DateTime expiration);
void Set<T>(string key, T value, TimeSpan sliding);
void Set<T>(string key, T value, CacheExpiration expiration);
void Set<T>(string key, T value, CacheSliding sliding);
void Remove(string key);
void ClearAll();
}
ThreadSafe GetOrSet
As any good cache should, the CacheRepository is thread safe and can be treated as a singleton.
Even better, the GetOrSet methods lock on set. This means that 10 threads could be trying to load the same cache value simultaneously, but only one will actually trigger a load and set. This helps redundant resource loads and database calls and keep your application running optimally.
private T GetOrSet<T>(string key, Func<T> loader,
DateTime? expiration, TimeSpan? sliding)
{
// Get It
T value;
var success = TryGet(key, out value);
// Got It or No Loader
if (loader == null || success)
return value;
// Load It
return LockedInvoke(key, () =>
{
// Get It (Again)
success = TryGet(key, out value);
if (!success)
{
// Load It (For Real)
value = loader();
// Set It
if (value != null)
Set(key, value, expiration, sliding);
}
return value;
});
}
Configurable Expiration Enums
Instead of being forced to set each of your cache expirations separately, you now have the option to use an enum value to group your cache expirations. Enums are available for both absolute expiration and sliding expiration.
You may override the duration of each cache key in your app config; this is really useful for when you want to uniformly modify your cache expirations in your QA or testing environments. Additionally, you may override the CacheRepositoryBase.GetConfigurationValue method to pull this configuration for anywhere you want, not just the ConfigurationManager.
public enum CacheExpiration
{
VeryShort = 10, // Ten Seconds
Short = 60, // One Minute
Medium = 300, // Five Minutes
Long = 3600, // One Hour
VeryLong = 86400 // One Day
}
<configuration>
<appSettings>
<add key="CacheExpiration.VeryShort" value="15" />
<add key="CacheExpiration.Short" value="90" />
ByType Extensions
Transparent cache key management is offered through a series of ICacheRepository extension methods. This makes caching even easier, as you don't need to worry about cache key collisions.
Using these extension methods, you many cache a Cat object with an Id of 1 and a Dog object with an Id of 1 in the same manner. The extension methods will create a key prefix based on the type and then use the specified identified as the suffix.
[Fact]
public void SameKeyDifferentType()
{
var setCat = new Cat { Name = "Linq" };
CacheRepository.SetByType(1, setCat);
var setDog = new Dog { Name = "Taboo" };
CacheRepository.SetByType(1, setDog);
var getCat = CacheRepository.GetByType<Cat>(1);
Assert.Equal(setCat.Name, getCat.Name);
var getDog = CacheRepository.GetByType<Dog>(1);
Assert.Equal(setDog.Name, getDog.Name);
}
Web Implementation & Dependency Injection via Unity
The CacheRepository.Web NuGet package includes a WebCacheRepository implementation that leverages System.Web.Caching.Cache. This is a very simple, but very effective, production ready implementation of the CacheRepositoryBase.
It should also be noted that this implementation is not only useful in ASP.NET, the System.Web.Caching.Cache is located in the System.Web library, but it still available outside of a web context. This means that this implementation can be used in other applications, including but not limited to Windows Services.
public class WebCacheRepository : CacheRepositoryBase
{
private readonly Cache _cache;
public WebCacheRepository()
{
_cache = HttpContext.Current == null
? HttpRuntime.Cache
: HttpContext.Current.Cache;
}
Wiring the cache repository to be injected into your controllers via Unity is also very easy. Just register the WebCacheRepository for the ICacheRepository interface, and be sure to provide a ContainerControlledLifetimeManager for optimal performance.
To use the implementation below, you will need to include the Unity.MVC3 NuGet Package to gain access to the UnityDependencyResolver.
public static void Initialise()
{
var container = BuildUnityContainer();
DependencyResolver.SetResolver(new UnityDependencyResolver(container));
}
private static IUnityContainer BuildUnityContainer()
{
var container = new UnityContainer();
container.RegisterType<ICacheRepository, WebCacheRepository>(
new ContainerControlledLifetimeManager());
return container;
}
If you missed the links above, here they are again:
Enjoy,
Tom
