Huge traffic, Transactions, CMS as a platform, Decoupled implementations

I was inspired by a webinar I recently attended, Architecting Growth–How to Crush Million Dollar Projects by Pantheon – a geek friendly managed host for enterprise WordPress and Drupal clients. This webinar is presented by their co-founder and discusses much of what they’ve learned providing infrastructure for larger scale projects.

This presentation covers their content management system (CMS) software-as-a-service (SaaS) delivery model in addressing scalability problems often seen in eCommerce, viral causes, campaigns, and news cycle use cases. Some challenges that arise from these use cases are:

Conventional wisdom holds that CMS systems cannot well handle large scale traffic. They get into their methodology of combining heavy caching with horizontal scaling architecture and DevOps best practices to make the CMS powered enterprise work at scale.

Here’s a bit about their caching and scaling architecture:

General recommendations for scaling CMS sites:

Empower multiple teams that utilize common back end features with their various front end systems. A broader development team manages the core system while site specific development is managed by local developers. This continuous integration (CI) pattern of development uses a release flow that beings with an upstream core site, feeding individual development sites, then staged and released to canary production sites, then less customized production sites, followed by the heavier production sites.