65 There’s also the underappreciated benefit of greater sustainability. While we tend to concentrate on speed increases, there’s another side to the story: more efficient operations. Even if our customers don’t need the increased speed, they’re able to deliver the same experience with reduced computing resources, meaning less environmental impact and greener operations for everyone. There’s just no question that .NET 5 has given Content Cloud a significant leap in performance, equivalent to what might be seen after making large scale hardware or architecture changes. With these improvements, we’ve eliminated a lot of acrobatics that content management systems developers across the industry have typically implemented to improvement their site performance. Our chief product officer, Justin Anovick, explains why the change was necessary. “Our partners and customers were ready to move to the latest .NET release, and when we did some benchmarking around performance, it was obvious there were so many reasons to make the move,” he says. “It was a significant investment, but we’re through it now and the result is better than we ever expected.” At Optimizely, we feel like this was a necessary step in our evolution. We’ve always had a close relationship with the Microsoft technology stack, and our future plans around version-less instances and low-code developer experiences required us to get onto the leading edge to avoid any disruptions down the road as our service model evolves. Deane Barker is senior director of content management strategy at Optimizely “The preliminary performance improvements that we’ve seen as a result have been stellar”
RkJQdWJsaXNoZXIy NzQ1NTk=