Bobby Bouwmann :: Surviving Large Applications
summary
Laravel monolith runs on MySQL in Kubernetes with 13 TB total data (9 TB core), ~17,750 API pods, 3,500–4,100 workers, 148 queues and processes 51 million jobs a day; team is 16 engineers. Concrete practices: keep framework defaults, use PHPStan/Pint and Pest, place tests next to classes, prefer jobs for async work and notifications as API wrappers, split code into product/external directories, schedule upgrades infrequently and avoid single‑person bus factors by enforcing consistency and heavy automated testing.
AI-written summary · about
chapters (25)
- 0:00Intro
- 0:16He hospitable
- 0:52Surviving large applications
- 1:12Every application is different
- 1:48Legacy code
- 2:05MyQ database
- 3:38Larl
- 3:55Rules
- 5:21Ingredients
- 9:27Documentation
- 10:46Million Dollar Engineer
- 11:23Bus Factor
- 13:15Keeping your application up to date
- 15:52Team size
- 16:30Application structure
- 17:30External directory
- 19:05Modular Larell
- 19:53Monolith
- 20:25Development Rules
- 21:58Take Time
- 22:50Tests
- 24:23Notifications
- 25:59Jobs
- 27:28Summary
- 28:28Questions
related talks
44mBuilding a complex product while scaling a team and a business on Laravel
28mCultivating success with Laravel
32mHow we abused PHP and Laravel to do Big Data.
46mHow I Built and Scaled a SaaS Product Using Laravel
25mLess Pain with Gain, how Laravel helps you scale your Applications
49mLaravel - If, how and why you should use it!
46mScaling With Friends
48m12 Factors Laravel