Skip to main content

A DD4T.net Implementation - A Component Factory that Caches

A DD4T ComponentFactory is in charge of retrieving or searching for IComponent models by using either serving them from local cache or delegating the call to a ComponentProvider that uses the Tridion Broker API to look things up in the Content Delivery database.

When retrieving Component models, the ComponentFactory uses a couple of methods that take as parameters the TcmUri of the Component and a Component Template TcmUri.

    IComponent GetComponent(string componentUri, string templateUri = "");
    bool TryGetComponent(string componentUri, out IComponent component, string templateUri = "");


The default ComponentFactory from DD4T .net v1.31 has been written in a relaxed fashion, and don't enforce a mandatory Component Template TcmUri. If a lazy developer chooses not to pass a templateUri, the code still works. However, the call to the Content Delivery database is not cached. This results in performance degradation when the internal DD4T cache is expired, and a new call to a previously retrieved Component is made. The request will make all its way to the database.

This issue can easily be prevented by passing a Component Template TcmUri to these two methods. However, developers being lazy people, I want to enforce the second parameter to be passed and to have a valid TcmUri in it.

As such, I created my own CachingComponentFactory class as a specialization of the DD4T default ComponentFactory, where I overrode the two methods:

    public class CachingComponentFactory : ComponentFactory, IComponentFactory
    {
        public new IComponent GetComponent(string componentUri, string templateUri)
        {
            if (!UriHelper.IsValidTcmUri(templateUri))
            {
                throw new ComponentNotFoundException();
            }

            return base.GetComponent(componentUri, templateUri);
        }

        public new bool TryGetComponent(string componentUri, out IComponent component, string templateUri)
        {
            if (!UriHelper.IsValidTcmUri(templateUri))
            {
                component = null;
                return false;
            }

            return base.TryGetComponent(componentUri, out component, templateUri);
        }
    }


The code is very straight forward and expects the second TcmUri parameter to be passed and to be a valid TcmUri. Anything else results is a ComponentNotFoundException.

The only thing left to do is to wire up my CachingComponentFactory in Ninject so that it is used every time an IComponentFactory instance is requested.

    Bind<IComponentFactory>().To<CachingComponentFactory>().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