Cloud

This article covers what you need to know to apply the necessary Security Headers to lock down your Headless Sitecore solution at the application layer. We're using a NextJS Headless solution deployed to Vercel and Sitecore CMS deployed to Azure PaaS.

In a previous post I discussed the management conundrum of Solr and Sitecore and the challenges faced with their differing eco-systems. This post will be more of a technical guide looking at how to configure SearchStax for your Sitecore Solution.

Solr is such an amazingly powerful product full of great features which is hard to beat however the challenge faced by most companies or Sitecore Development shops is that traditionally, Solr is hosted in a totally different ecosystem.

Often when having discussions with clients using Azure PaaS about DR and the available options, the ideal scenario comes at a sigificant cost.() LINQ to Sitecore capability.

During the move to Azure PaaS there have been a few instances where we've noticed a series of errors being logged about file I/O issues which often result in instances dying within a PaaS "load balancer".

It's been quite some time since we started our journey using Sitecore 8.2 and Azure PaaS. There has been no small amount of experimentation, failings and most importantly, learnings as we worked towards an automated build and release pipeline using VSTS so I thought I would take the opportunity at long last to share some of my experiences.

For quite a few months now, my workplace has been looking at moving our website from a fully automated, cloud-based AWS solution over to Azure. Every person I've mentioned this to has had a similar reaction, mostly of disbelief. "AWS is far more mature and robust cloud offering".