Caring much about the performance of my code, this blog post is a continuation of my serial about performance optimization of Episerver solutions. This time I reveal eight common issues affecting performance, along with suggested solutions to each. Some of those issues are actually very common across projects and developers.

Caching is great! Caching can make a slow site fast, and a fast site blazingly fast. But how to cache custom objects that rely on Episerver content, in a way that is simple, safe and performant way?

Enabling long term caching of static frontend files is good for the performance of both servers and browsers. However, to instantly force a re-download of files following a new release, cache busting solution is needed. This is an update to my original cache busting solution and blog post. It is more lean and efficient and supports ASP.Net Core, too.

I were recently tasked with creating code to render PDF files containing Arabic words using PdfSharp. Unfortunately, PdfSharp does not support Arabic or other right-to-left languages. Here is the workaround I made up.

I was missing some features and scalability from the built-in InRiver iPMC extension log. Therefore I did an integration that demonstrates how to log events, exceptions and metrics to Azure Application Insights (using it as a supplementary log service).

Usually importing images from a "hot folder" to iPMC would require a scheduled extension. But it can also be made serverless. See my demonstration here.

For a long time, transactional emails have been sent directly from Episerver, by rendering and sending a CMS page as an email. In this post I suggest another approach, where we simply tell SendGrid which template to use and what data to put in the template placeholders.

Since moving to Dubai, I have heard and read a lot about GraphQL as a new model for implementing API's for web and native apps. However, I have not yet seen it applied to Episerver CMS or Commerce. So, for this blog post, I created a small demonstration of a GraphQL API, based on Episerver's Quicksilver sample site. Read about the outcome here.

Last month I switched from Google Analytics to Yandex.Metrika as my analytics suite.In this blog post, I explain why I chose Yandex.Metrika and why I believe it is a great and powerful tool.

When I finished preparing the code for another blog post, I had to add a LICENSE and a README file to the Git repository of my code. Adding those files to the very first commit and adding a copyright notice to all C# source files, required rewriting of Git history. In this blog post, I share the scripts I used myself.