These four architectural blueprints show how to optimize CMS deployment to the cloud, using Amazon Web Services (AWS) and Magnolia CMS as an example. We discuss the advantages and disadvantages of each approach and offer recommendations to achieve autoscaling for high-performance and high-traffic scenarios. The four blueprints cover:
- Standard CMS deployment
- Deployment with content source target
- Deployment with JCR clustering
- Deployment with RabbitMQ activation
To find out how we handle and store your data, please have a look at our privacy policy. We won't send you any marketing emails without your permission and you can always update your preferences or opt out at any time.