Refactoring to Symfony Components
summary
Refactors a messy, high‑traffic news site into a PSR‑autoloaded codebase over ~4 months using symfony2 components, Composer, the class loader, the Router, EventDispatcher, HTTP Foundation, YAML config, pimple for dependency injection, Twig for templating and Swift Mailer for email; introduces lazy services, event‑based email/notifications, template and route caching, and simple queuing; YAML parsing proves CPU‑heavy and one-line cleanup yields a 40% CPU gain; deployment swaps servers over a weekend and the staged refactor succeeds faster and with less risk than a full rewrite.
AI-written summary · about
chapters (25)
- 0:00Introduction
- 0:52The Components
- 4:02Swift Mahler Twig
- 10:20Caching
- 10:33dependency injection container
- 17:18XML file parsing
- 18:35XML file caching
- 30:33Dispatch Event
- 30:49Gotcha
- 32:26Twig
- 33:57Pimple
- 37:43HTTP Foundation
- 39:03Content Type Translation
- 39:43Swift Mailer
- 40:54Moving for 4 days
- 41:28Overtime
- 42:04Business Logic
- 43:34Business Logic Issues
- 45:24Legacy Apps
- 46:20Project Size
- 47:17Files Methods
- 47:36New Features
- 48:19Deployment
- 49:31Functional Tests
- 50:02Challenges
related talks
57mEating spaghetti with Symfony
48mDeveloping Symfony applications in 2023
01h 00mStandardization, the Symfony Way
41mMinimal Symfony in real life
57mRefactoring a large legacy PHP Application: a case study
45mMessy data != Messy code
48mBuilding Really Fast Applications
01h 01mDeep dive into Symfony 4 internals