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

Scaling Policies

This post is part of a bigger topic Autoscaling Publishers in AWS . In a previous post we talked about the Auto Scaling Groups , but we didn't go into details on the Scaling Policies. This is the purpose of this blog post. As defined earlier, the Scaling Policies define the rules according to which the group size is increased or decreased. These rules are based on instance metrics (e.g. CPU), CloudWatch custom metrics, or even CloudWatch alarms and their states and values. We defined a Scaling Policy with Steps, called 'increase_group_size', which is triggered first by the CloudWatch Alarm 'Publish_Alarm' defined earlier. Also depending on the size of the monitored CloudWatch custom metric 'Waiting for Publish', the Scaling Policy with Steps can add a difference number of instances to the group. The scaling policy sets the number of instances in group to 1 if there are between 1000 and 2000 items Waiting for Publish in the queue. It also sets the

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

Toolkit - Dynamic Content Queries

This post if part of a series about the  File System Toolkit  - a custom content delivery API for SDL Tridion. This post presents the Dynamic Content Query capability. The requirements for the Toolkit API are that it should be able to provide CustomMeta queries, pagination, and sorting -- all on the file system, without the use third party tools (database, search engines, indexers, etc). Therefore I had to implement a simple database engine and indexer -- which is described in more detail in post Writing My Own Database Engine . The querying logic does not make use of cache. This means the query logic is executed every time. When models are requested, the models are however retrieved using the ModelFactory and those are cached. Query Class This is the main class for dynamic content queries. It is the entry point into the execution logic of a query. The class takes as parameter a Criterion (presented below) which triggers the execution of query in all sub-criteria of a Criterio