Sitecore caches are one of the most overlooked but critical components for Sitecore platform stability. The caches across both the Content Management and Content Delivery roles can have either a positive impact on performance, or a negative one if not tuned properly. The Sitecore Community Site puts it best when they state: Sitecore uses various …
While the release of Sitecore 10 offered much more personalization options with Sitecore XM, it lacked the capability to leverage the Sitecore Geolocation Service. However, starting with Sitecore 10.1, you can now use the Sitecore Geolocation Service in Sitecore XM! This is an exciting development for those who need some level of personalization and geo …
When deploying Sitecore via the Sitecore Installation Framework (SIF), installing the prerequisites is critical. However, due to a few outdated file links, it will not execute properly and generate an error such as: The outdated links are resolved in the SIF for Sitecore Version 10.1.1 (10.1 Update 1). Depending on your Sitecore version, you will …
A Composable DXP offers several distinct benefits, but like all things, has a few converse challenges. This does not mean the challenges disqualify a Composable DXP such as Sitecore SaaS from your list of options, but rather before making the jump… its critical to evaluate the pros and cons of a Composable DXP. What is …
With Sitecore SaaS and the move to a Composable DXP, the Four51 acquisition will play a key role in newer Commerce offerings. While awaiting for what the new Commerce solution will look like under the hood, it may be helpful to understand the Four51 platform as it stands today. The “Sitecore OrderCloud” spoke to at …
If you are struggling to resolve a 500 Error when accessing the Business Tools from your Sitecore CMS, there may be a surprising reason for it. Typically, a Sitecore PaaS environment has a self signed certificate for communication in between Apps. This is set via the ARM template when the environment is deployed, but may …
xConnect is a key component of a XP Sitecore implementation, however it may be overkill for your personalization needs. Starting with Sitecore 10.0.0, Sitecore XM offers some base personalization options depending if you implemented XP with CMS Only Mode or just deployed a scaled XM build. In Sitecore 9.3, it stated the following: If you …
Session State is a critical component of the Sitecore ecosystem. Redis is typically leveraged in this regard, alongside the correct Redis settings, and the scale of a C1 only offers “low network bandwidth” which can create bottlenecks, especially when under Production load. While the total Redis cache size may appear adequate, it is this oft-overlooked …
If you are wondering why when deploying your Sitecore environment there is no Reporting role, it is because as of Sitecore 10.1, it is now combined with the CMS. Specifically:
In Sitecore 10.1 and later, the xDB Reporting role has been combined with the Content Management role.
https://doc.sitecore.com/en/developers/101/platform-administration-and-architecture/experience-platform-roles.html
Please review the “Architecture and Roles” documentation for Experience Platform to review the available roles supporting XP via the following documentation: Experience Platform roles (sitecore.com)
Note that there are separate roles by type if you are confused which roles belong to which part of Sitecore (ex. XM, XP, and XC) per the Sitecore 10 Application Roles, Storage Roles, and Indexes article).
Redis is a critical component for Session State (both Private and Shared) in a Sitecore environment, and its easy to take a “set it and forget mindset” when it comes to using Redis with Sitecore. However, there is a lot of tuning and practices to optimize Redis for Sitecore. Here are 4 Quick Redis Tips …