Multi-Experience Operations
Core Concepts
| Site instances | Is the concrete deployment of a site in a specific environment and represents the actual running website with its database, files, and domain configuration. |
|
| Feature | Multi-Experience Operations | Traditional Hosting |
|---|---|---|
| Code Management | Single shared codebase | Separate repository per site |
| Deployments | Bulk deployments across sites | Individual site deployments |
| Consistency | Automatic consistency | Manual synchronization |
| Scaling | Centralized management | Linear complexity increase |
| Multi-Experience Operations | Site Factory |
|---|---|
| Supports independent code deployment at environment level. | Does not support independent code deployment for each site. |
Supports isolation for sensitive sites. | Does not support resource isolation for sites. |
| Supports multiple production environments and therefore, sites grouped on an environment can run on different versions of code. | Cannot run different sites on different versions of code. |
To work with MEO, an understanding of the architectural hierarchy from code base to environment to site instances is mandatory.
Code Deployment Constraints: Code deployment must occur at the environment level to update every site instance simultaneously. The platform does not support code deployment to a single isolated site. Furthermore, all sites on a single environment share the same pods rather than run in isolation.
Infrastructure and Platform Limits: Because MEO builds upon Cloud Next infrastructure, application designs must respect Cloud Next platform constraints. Application configurations must adhere to Cloud Next limits for MySQL versions and cron job executions because Cloud Classic limitations no longer apply.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Code Deployment Constraints: Code deployment must occur at the environment level to update every site instance simultaneously. The platform does not support code deployment to a single isolated site. Furthermore, all sites on a single environment share the same pods rather than run in isolation.
Infrastructure and Platform Limits: Because MEO builds upon Cloud Next infrastructure, application designs must respect Cloud Next platform constraints. Application configurations must adhere to Cloud Next limits for MySQL versions and cron job executions because Cloud Classic limitations no longer apply.
If this content did not answer your questions, try searching or contacting our support team for further assistance.
Multi-Experience Operations