en https://world.optimizely.com/blogs/szokowski-blog/60Optimizely World https://szolkowski.github.io/2026/04/13/OptiPowerTools-Hangfire-2.0-CMS-13-Support When I released OptiPowerTools.Hangfire back in March, it targeted Optimizely CMS 12. With CMS 13 now out and running on .NET 10, it was time to bring the package along. Version 2.0.0 adds full CMS 13 support, and I also shipped 1.0.1 on the CMS 12 line with sample jobs to help people get started faster. https://szolkowski.github.io/2026/04/13/OptiPowerTools-Hangfire-2.0-CMS-13-Support Mon, 13 Apr 2026 09:00:00 GMT Blog post https://szolkowski.github.io/2026/04/09/optimizely-alloy-on-macos-apple-silicon In my first Apple Silicon post and the 2025 revisit I covered running an Optimizely Foundation site on an M1/ARM Mac. This time I wanted to try something smaller — the official Alloy template site for Optimizely CMS 13, which ships with a ready-made Docker Compose setup. On Windows it works out of the box, but on macOS with Apple Silicon a few adjustments are needed before everything runs smoothly. https://szolkowski.github.io/2026/04/09/optimizely-alloy-on-macos-apple-silicon Thu, 09 Apr 2026 09:00:00 GMT Blog post https://szolkowski.github.io/2026/03/31/OptiPowerTools.Hangfire-A-Drop-in-Hangfire-Integration-for-Optimizely-CMS-12 Back in 2024, I wrote a post on Adding Hangfire to Episerver/Optimizely CMS 12, walking through each step of integrating Hangfire into an Optimizely project — the authorization filter, the controller, the view with an iframe, the menu provider, the startup wiring. It was a fair amount of boilerplate, but it worked and people found it useful. https://szolkowski.github.io/2026/03/31/OptiPowerTools.Hangfire-A-Drop-in-Hangfire-Integration-for-Optimizely-CMS-12 Tue, 31 Mar 2026 08:00:00 GMT Blog post https://szolkowski.github.io/2026/03/03/Catalog-Traversal-with-Hangfire-Part-3-Advanced-Job-Management In Part 1, I showed how to build a memory-efficient catalog traversal service, and in Part 2, I demonstrated practical patterns using Optimizely’s built-in scheduled jobs. https://szolkowski.github.io/2026/03/03/Catalog-Traversal-with-Hangfire-Part-3-Advanced-Job-Management Tue, 03 Mar 2026 08:00:00 GMT Blog post https://szolkowski.github.io/2026/02/24/Catalog-Traversal-in-Action-Part-2-Real-World-Scheduled-Job-Patterns In my previous post, I showed how to build a memory-efficient catalog traversal service for Optimizely Commerce. The service uses streaming to process large catalogs without loading everything into memory at once. https://szolkowski.github.io/2026/02/24/Catalog-Traversal-in-Action-Part-2-Real-World-Scheduled-Job-Patterns Tue, 24 Feb 2026 08:00:00 GMT Blog post https://szolkowski.github.io/2026/02/18/Memory-Efficient-Catalog-Traversal-in-Optimizely-Commerce-Part-1-Building-the-Service If you’ve worked with Optimizely Commerce for any length of time, you’ve probably faced this scenario: you need to process an entire product catalog in a scheduled job. Maybe you’re syncing to an external PIM system, exporting data for analytics, or performing bulk updates. The straightforward approach of loading all products into memory works fine for small catalogs, but once you hit thousands of products, things start to get uncomfortable. https://szolkowski.github.io/2026/02/18/Memory-Efficient-Catalog-Traversal-in-Optimizely-Commerce-Part-1-Building-the-Service Wed, 18 Feb 2026 08:00:00 GMT Blog post https://szolkowski.github.io/2026/01/18/Memory-Efficient-Catalog-Traversal-in-Optimizely-Commerce-Part-1-Building-the-Service If you’ve worked with Optimizely Commerce for any length of time, you’ve probably faced this scenario: you need to process an entire product catalog in a scheduled job. Maybe you’re syncing to an external PIM system, exporting data for analytics, or performing bulk updates. The straightforward approach of loading all products into memory works fine for small catalogs, but once you hit thousands of products, things start to get uncomfortable. https://szolkowski.github.io/2026/01/18/Memory-Efficient-Catalog-Traversal-in-Optimizely-Commerce-Part-1-Building-the-Service Sun, 18 Jan 2026 08:00:00 GMT Blog post https://szolkowski.github.io/2025/10/08/Quiet-Performance-Wins-Scheduled-Job-for-SQL-Index-Maintenance-in-Optimizely As Optimizely CMS projects grow, it’s not uncommon to introduce custom tables—whether for integrations, caching, or specialized business logic. But with great schema comes great responsibility: SQL Server indexes and statistics need love too. https://szolkowski.github.io/2025/10/08/Quiet-Performance-Wins-Scheduled-Job-for-SQL-Index-Maintenance-in-Optimizely Wed, 08 Oct 2025 08:00:00 GMT Blog post https://szolkowski.github.io/2025/09/04/automatically-removing-orphaned-jobs-from-db Optimizely CMS provides a simple yet powerful built-in job system that handles most standard scheduling scenarios with ease. Developers can easily implement these jobs to run automatically on a defined schedule or trigger them manually through the CMS interface. From my experience as an Optimizely/Episerver developer, manual jobs are especially useful for one-off operations or bulk content updates. Typically, these jobs serve a temporary purpose and are removed from the codebase in subsequent releases once they’ve fulfilled their role. https://szolkowski.github.io/2025/09/04/automatically-removing-orphaned-jobs-from-db Thu, 04 Sep 2025 08:00:00 GMT Blog post https://szolkowski.github.io/2025/06/12/episerver-and_application_insights_filters Application Insights is a cloud-based service designed to monitor web applications, providing insights into performance, errors, and user behavior, which integrates very well with the Optimizely CMS/Commerce solution and is included in the default DXP experience. However, like any generic tool for complex systems, it can be tuned to work even better for specific platforms and projects. https://szolkowski.github.io/2025/06/12/episerver-and_application_insights_filters Thu, 12 Jun 2025 08:00:00 GMT Blog post https://szolkowski.github.io/2025/05/26/episerver-on-apple-silicon-2025 A few years ago I posted post about how to run Optimizely/Episerver on M1 (ARM) based machine, so I think it is high time to revisit and check what did change. https://szolkowski.github.io/2025/05/26/episerver-on-apple-silicon-2025 Mon, 26 May 2025 08:00:00 GMT Blog post https://szolkowski.github.io/2024/07/31/adding-hangfire-to-epi-12 Episerver/Optimizely contains build ScheduledJobs support which does its job for internal EPI jobs and simple custom cases, however, when the app grows and we need more and more jobs it fails behind dedicated solutions. https://szolkowski.github.io/2024/07/31/adding-hangfire-to-epi-12 Wed, 31 Jul 2024 12:57:48 GMT Blog post https://szolkowski.github.io/2024/07/11/adding-hangfire-to-epi-12 Episerver/Optimizely contains build ScheduledJobs support which does its job for internal EPI jobs and simple custom cases, however, when the app grows and we need more and more jobs it fails behind dedicated solutions. https://szolkowski.github.io/2024/07/11/adding-hangfire-to-epi-12 Thu, 11 Jul 2024 10:46:48 GMT Blog post https://szolkowski.github.io/2023/08/15/add-sonarcloud-to-epi-12-pipeline In my previous post Add Github pipelines/workflows to Episerver 12 project I have briefly explained how to add simple pipeline/workflow to Episerver/Optimizely 12 project. Having project build for each PR and on main branch push is nice improvement, but we can make it even better. For this example I will add SonarCloud integration to my existing workflow from my previous post. You can see it on my Foundation fork - it will be using Github actions on each pull request and on main branch. https://szolkowski.github.io/2023/08/15/add-sonarcloud-to-epi-12-pipeline Tue, 15 Aug 2023 17:31:48 GMT Blog post https://szolkowski.github.io/2022/07/30/add-github-pipeline-to-epi-12 With Episerver 12 moving to .NET 5/6 civilization come to devops handling of Episerver projects and we can easily integrate modern CI approaches using pipelines. For this example I will add simple building of my Foundation fork using Github version of pipelines called “workflows” on each pull request and on main branch. https://szolkowski.github.io/2022/07/30/add-github-pipeline-to-epi-12 Sat, 30 Jul 2022 15:31:48 GMT Blog post https://szolkowski.github.io/2022/07/28/episerver-on-apple-silicon With introduction of .NET 6 Episerver/Optimizely packages developing it on M1 machine is now possible, however there are still some problems with initial configuration, but lets not go ahead of ourself. https://szolkowski.github.io/2022/07/28/episerver-on-apple-silicon Thu, 28 Jul 2022 19:29:19 GMT Blog post