Growing Your Laravel Application Infrastructure
summary
Start with one small server running web, DB, Redis and workers and tune DB memory, max connections, FPM workers and open file limits as traffic grows. When scaling hits a limit, separate the database, then split workers and add a dedicated cache server (Redis) so queues don’t hit the DB. Auto-scale identical web or worker instances behind a load balancer but watch for load balancer buffering to disk and DB connection limits. Use read replicas (multiple reads, one write), migrate IPs for rolling upgrades, and evaluate colo vs cloud costs.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker background
- 3:13Starting with a single server setup
- 6:06Scaling up vs scaling out
- 9:19Separating database and application layers
- 10:03Dedicated worker and web servers
- 12:14Swarming servers for scalability
- 14:47Load balancer considerations
- 15:29Database redundancy and read replicas
- 16:59Future-proofing infrastructure
- 18:47Advanced load balancing topics
- 20:13Cost comparison of infrastructure options
- 21:40Q&A session
related talks
37mScaling LAMP doesn't have to suck
44mIntroduction to application scaling
32mWordPress Scalability
39mLaravel: 7 Steps to Dramatically Improve Performance
31mFrom Runtime to Resilience: Scaling PHP
25mWriting resilient code
41mForget Scaling: Focus on Performance
47mFrom Legacy to High-Load: Evolution of a Web Application