I made a new Redis PubSub event provider for Optimizely, for use with load-balanced servers that cannot use my .NET sockets event provider. Read about it, and get it, here.

If you are working with Optimizely DXP sites, take a few minutes to consider whether you really need sticky sessions. Here is how to disable them and what happens after.

For all of you that work on sites with mini-carts, here is a performance tip for Optimizely Customized Commerce.

Since Optimizely CMS can now be deployed as a Docker container, here is a demonstration of building, running and scaling an Optimizely CMS 12 site on a Docker Engine swarm.

With Optimizely CMS 12 now fully multi-platform, it can now be hosted in new ways. Here is a quick walkthrough of some of the hosting models.

There is a new event provider for the Optimizely CMS 12+ platform, for use in on-premise hosting scenarios. It is simple and efficient.

Here is how to ensure that Azure Application Insights logs and performance are not lost on shutdown, all while also optimizing log collection.

If you return large responses from your custom Web APIs or from Episerver Content and Service APIs, you might want to remember about response compression. Read here about enabling it.

From working on Episerver solutions with native apps, I have done several learnings on challenges, limitations and solutions. In this blog post, I list up five of them.

This is the story about how an Episerver site achieved extreme performance for some landing pages, by applying distributed output caching using Episerver DXC and Cloudflare.