Global Availability & Data Residency

Adobe Experience Manager’s architecture uses globally distributed, and redundant content delivery networks (CDN) to ensure high availability. These CDNs deliver your content to points of presence (POP) globally, which makes it hard to restrict data residency.

Your sites, globally available

The two highest priorities in delivering web experiences are availability and performance. For this reason, we use multiple content delivery networks to provide the Adobe Experience Manager service. Multiple CDNs, so that in the rare case of a CDN outage we can switch the full delivery stack to a separate, unaffected CDN and provide continued high availability.

Each of the CDNs uses dozens to thousands of different points of presence, these are high-performance caching servers located close to critical internet infrastructure in global locations close to population centers. These POPs do cache the content served for your websites and make it available to visitors.

Your content, globally distributed

In order to ensure this global availability of your sites, your content has to be globally distributed. Each of the core storage areas of the AEM content hub (media, content, code) is therefore equally globally distributed and outside of legal restrictions, there is no way to ensure content storage is restricted to or from particular geographical locations.

Some geographic locations may restrict access to your content, for details see the next article in this guide.

What about data residency

With content intentionally globally distributed, you may wonder about data residency. Data residency refers to the legal requirement to collect, process, and store personal data in the country or region where the data residency law applies.

Data residency does not apply to the content you are publishing nor does it apply to the Real User Monitoring (RUM) data Adobe is collecting, as it includes no personal data.