Skip to main content

A DD4T.net Implementation - A Simple TTL Cache

In this post I'll talk about a very simple cache implementation for DD4T using the standard .NET System.Web.Caching.Cache class and that allows NULL cached values. The cache itself has no invalidation mechanism and it solely uses a Time-To-Live (TTL) mechanism to expire/evict cached elements.

I used the entire cache wrapper that Rob graciously shared in his post Labels In Dynamic Delivery For Tridion:
  • The ICacheWrapper interface that defines the cache method signatures;
  • The WebCacheWrapper class implementing the ICacheWrapper interface;
In its standard form, Rob's WebCacheWrapper does not allow NULL values to be stored in the cache. Or better yet, it allows them to be stored, but when retrieved, the TryGet method will return false indicating a cache miss.

I personally am a big fan of allowing NULLs to be cached. Take for example, the ability to save the result of a costly operation that resulted in NULL, such as a database lookup for some entity that doesn't actually exist in the DB. In a high-availability environment, one must improve the performance of every single call, thus DB checks that return null must be cached as well.

In order to allow NULLs in DB, I resorted to store something else instead in the cache. Something meaningless in size (1 bit if possible) that would indicate my pseudo-NULL. I chose to store a boolean false as an indication of NULL.

When retrieving the cached value, I'm simply trying to cast the value to the type I requested. If the cast fails (due to the fact that boolean false can't be cast to another object), then I assume a NULL was cached.

The sample code below is from the ModelFactory class discussed in an earlier post. The goal is to cache built models, so that we don't have to load them from the Content Delivery database and convert them into strongly-built models on every invocation of the ModelFactory method.

    public T GetModel<T>(string componentUri) where T : ModelBase
    {
        T model = null;
        object cacheElement;
        string key = BuildTheKey(componentUri);

        if (CacheWrapper.TryGet(key, out cacheElement))
        {
            model = cacheElement as T;
        }
        else
        {
            // fetch the actual model

            if (model == null)
            {
                CacheWrapper.Insert(key, false, 1);
            }
            else
            {
                CacheWrapper.Insert(key, model, cacheMinutes);
            }
        }

        return model;
    }

The simplified code above attempts to cast the cacheElement to the generic type T that is a specification of ModelBase. If the cast fails, a null model is returned. However, when the cast succeeds, we know that a valid model has been cached and now retrieved from cache.

Upon inserting a model into the cache, we check whether the model is null and if so, then we insert a boolean false with a TTL of 1 minute. Otherwise, the actual model is cached using the pre-configured TTL cacheMinutes.

The property CacheWrapper is of type ICacheWrapper and it is injected into the ModelFactory class using Ninject. More information about dependency injection in DD4T .net, in this post:

    [Inject]
    public virtual ICacheWrapper CacheWrapper { get; set; }

Of course this implies there is a binding in Ninject from ICacheWrapper to the implementing WebCacheWrapper:

    Bind<ICacheWrapper>().ToMethod(context =>
        new WebCacheWrapper(HttpRuntime.Cache)).InSingletonScope();




Comments

Popular posts from this blog

Running sp_updatestats on AWS RDS database

Part of the maintenance tasks that I perform on a MSSQL Content Manager database is to run stored procedure sp_updatestats . exec sp_updatestats However, that is not supported on an AWS RDS instance. The error message below indicates that only the sa  account can perform this: Msg 15247 , Level 16 , State 1 , Procedure sp_updatestats, Line 15 [Batch Start Line 0 ] User does not have permission to perform this action. Instead there are several posts that suggest using UPDATE STATISTICS instead: https://dba.stackexchange.com/questions/145982/sp-updatestats-vs-update-statistics I stumbled upon the following post from 2008 (!!!), https://social.msdn.microsoft.com/Forums/sqlserver/en-US/186e3db0-fe37-4c31-b017-8e7c24d19697/spupdatestats-fails-to-run-with-permission-error-under-dbopriveleged-user , which describes a way to wrap the call to sp_updatestats and execute it under a different user: create procedure dbo.sp_updstats with execute as 'dbo' as

Content Delivery Monitoring in AWS with CloudWatch

This post describes a way of monitoring a Tridion 9 combined Deployer by sending the health checks into a custom metric in CloudWatch in AWS. The same approach can also be used for other Content Delivery services. Once the metric is available in CloudWatch, we can create alarms in case the service errors out or becomes unresponsive. The overall architecture is as follows: Content Delivery service sends heartbeat (or exposes HTTP endpoint) for monitoring Monitoring Agent checks heartbeat (or HTTP health check) regularly and stores health state AWS lambda function: runs regularly reads the health state from Monitoring Agent pushes custom metrics into CloudWatch I am running the Deployer ( installation docs ) and Monitoring Agent ( installation docs ) on a t2.medium EC2 instance running CentOS on which I also installed the Systems Manager Agent (SSM Agent) ( installation docs ). In my case I have a combined Deployer that I want to monitor. This consists of an Endpoint and a

Debugging a Tridion 2011 Event System

OK, so you wrote your Tridion Event System. Now it's time to debug it. I know this is a hypothetical situtation -- your code never needs any kind of debugging ;) but indulge me... Recently, Alvin Reyes ( @nivlong ) blogged about being difficult to know how exactly to debug a Tridion Event System. More exactly, the question was " What process do I attach to for debugging even system code? ". Unfortunately, there is no simple or generic answer for it. Different events are fired by different Tridion CM modules. These modules run as different programs (or services) or run inside other programs (e.g. IIS). This means that you will need to monitor (or debug) different processes, based on which events your code handles. So the usual suspects are: dllhost.exe (or dllhost3g.exe ) - running as the MTSUser is the SDL Tridion Content Manager COM+ application and it fires events on generic TOM objects (e.g. events based on Tridion.ContentManager.Extensibility.Events.CrudEven