A few days ago I showed how to correlate log telemetry in a Hangfire job on Optimizely. Here is a scaled-down version for regular scheduled jobs on Optimizely. #optimizely #episerver
https://stefanolsen.com/posts/telemetry-correlation-for-scheduled-jobs-in-optimizely/?utm_source=mastodon&utm_medium=social&utm_campaign=optimizely-scheduledjobs-telemetry
I often resort to using Hangfire on Optimizely websites that need a job queue or advanced job scheduling. And I apply these four tricks every time. #optimizely #episerver #hangfire
https://stefanolsen.com/posts/4-tips-and-tricks-for-hangfire-on-optimizely-cms/?utm_source=mastodon&utm_medium=social&utm_campaign=optimizely-hangfire-four-tips
#optimizely #episerver #hangfire
Sometimes I need to use a computed value several times in a page request. To not waste performance, I found a hidden helper in Optimizely CMS for very short-term caching. #optimizely #episerver
Here’s an analogy. When I go to a grocery shop, I always take a trolley or a cart on my way in. It’s more efficient than getting one when I take my first produce.
But on an Optimizely Commerce site it is different. Here it is more efficient to first create a cart when the customer first need it. I wrote a blog post about it.
Also, there is a bonus tip that can easily save some database load.
Here’s an analogy. When I go to a grocery shop, I always take a trolley or a cart on my way in. It’s more efficient than getting one when I take my first produce.
But on an Optimizely Commerce site it is different. Here it is more efficient to first create a cart when the customer first need it. I wrote a blog post about it.
Also, there is a bonus tip that can easily save some database load.