AEM | Considerations for Deciding Between One Global Instance and Multiple Regional Instances (e.g. Europe and US)


  • An instance can contain multiple web sites. Each web site can contain pages for multiple languages and locales (i.e. regions).
  • OSGI configurations are global (i.e. they apply universally across the entire instance) and are used to control things like how many old versions of a page to keep as a page goes through modifications or edits. Most OSGI configurations can be as loose or as tight as you want them to be. If they are loose, they allow more control at the individual web site level. If they are tight, they allow less control at the individual web site level.
  • All remaining elements of an AEM setup, such as user groups and users, assets (images, videos, PDFs), OSGI bundles, code, templates, components, rollout configurations, workflows, integrations, etc. can be seamlessly made available across an instance. Individual web sites can choose to reuse them or create their own.
  • Reuse is easier across a single instance but also achieved easily enough across multiple instances via shared code repositories and solutions like Connected Assets or cloud-based datastores.
  • Upgrading and patching occurs at the instance level. Two different instances at different version or patch levels may have difficulty sharing the same configurations, OSGI bundles, templates, components, rollout configurations, workflows, etc.
  • Unless you’re using AEM to define audience segments, your segment definitions can live in a single cloud instance of Target, Analytics, Audience Manager, etc. and be shared across instances.
  • If your instances are pointing to the same Analytics instance in the cloud, they can all feed the same (or different) Report Suites and it is possible to report globally across multiple AEM instances and domains, i.e. rollup or aggregate the data to a single Global Report Suite.
  • A 360/single-view of the customer is feasible either way via integration between your customer source of truth (e.g. CRM) and the CDP/DMP.
  • In summary, a global instance is a more tightly coupled solution than one with multiple regional instances. A global instance makes it easier to reuse content, code and configuration but a change that is made without adequate consensus or testing can negatively impact a large portion of the organization. To a lesser degree the same tradeoffs prevail at the instance level in the case of multiple regional instances.

Comments

Popular posts from this blog

Milwaukee Appliance Hand Truck

Utility trailer buying guide

My Experiments with the PICAXE 08M2+