Scaling a Monolith, Is A Four-Letter Word
summary
A Drupal CMS portal plus a Salesforce CRM and mobile client aims to handle 4 million users in 20 minutes without changing application code. Infrastructure changes include Kubernetes on AWS, CloudFront CDN, Elasticache (80% cache hit ratio), EFS shared storage, one RDS with two read replicas, connection pooling, Apache memory tweaks, node resizing and switching Ingress from NodePort to ClusterIP. Initial load tests show the site dies at 2 million due to DB connection exhaustion; after infra fixes the portal meets the target.
AI-written summary · about
chapters (7)
- 0:00Scaling a monolith challenge
- 1:53Project scope and team
- 4:04Technical stack and cloud
- 6:14Architectural scaling solutions
- 8:46Performance bottlenecks
- 9:50Optimizations and changes
- 10:53Outcomes and reflections
related talks
31mTo Kill a Monolith: Slaying the Demons of a Monolith with Node.js Microservices on CloudFoundry
46mScaling a Collaboration Service like Nextcloud to 20 Million users
38mFrom Monolith to Nimble
47mFrom Legacy to High-Load: Evolution of a Web Application
23mWhen to know you've outgrown your monolith
30mMonolith to Microservices
51mMicroservices and Microfrontends: Scaling, Learning, Growing
30mBringing it all together