Delivering The Sitecore Experience

As we all know, there are two main deployment topologies for Sitecore XP: Single - mostly for developer and integration environments Scaled - for all other environments This post is intended to cover regional deployment and scaling options for a fully scaled production PaaS deployment. There are three ways in which you can regionally scale Sitecore: Regionally scaled content delivery with shared xDB Regionally scaled content delivery with isolated xDB Regionally isolated Sitecore deployment Option #1 is the most common scaling option and works in the the following scenario: Content & experience management is regionally centralized Marketing operations, marketing automation and digital marketing activities in general are regionally centralized Web analytics collection is regionally centralized This basically means that operationally speaking, the organization is fairly centralized in their management and governance for the following: Content creatio

China has had strong data protection regulation for a while and it only seems to be getting tighter in 2019.  Increasingly, clients running Sitecore as their digital CXM platform require multi-regional deployments, and deploying solutions in the APAC region usually tends to pose a challenge. A couple of years ago, it may have been easy enough to simply carve out some infrastructure local to China and direct all local language variant traffic to the instance. But this is no longer sufficient. China seems to have taken a lot of articles from GDPR and continues to add to them and make privacy law even from stringent. Sitecore has quite a few provisions OOTB for handling some of the GDPR articles and the other can be handled via either solution design, custom implementation or system architecture. Here is are some of the ToDos related to CSL, CDPR as they relate to GDPR. Compliance via solution design & custom implementation CSL & GDPR: Implement consent and