If you've started delving into the world of Composable SaaS in recent times, you may have encountered a common issue when it comes to security and the typical existing Security Posture businesses have which doesn't quite align to the way in which Composable SaaS architectures need to work.
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.