Avoid Costly Framework Upgrades
summary
Claims that framework swaps stop being year‑long rewrites once controllers and models are decoupled: replace extends AbstractController with constructor injection and a templating adapter, move persistence into explicit repositories instead of ActiveRecord, and target dependency inversion everywhere. Uses PHPUnit unit tests and higher‑level HTTP tests, scripts to convert routing configs, and PSR standards like PSR-7/15 for portable handlers. Dozens of migrations show this cuts upgrade effort from many months to hours per module and keeps code testable and framework‑agnostic.
AI-written summary · about
chapters (8)
- 0:00Start
- 4:11Is the new version compatible?
- 8:15New framework version comes out.
- 18:19Dependency Inversion
- 30:08XML config files
- 31:29PSR for routing config would be nice.
- 36:56Do you really need an ORM?
- 44:00Framework Maintainers
related talks
25mCode decoupling from Symfony (and others frameworks)
13mTo Framework or Not to Framework? That is the Question
34mSustainable Architecture
01h 00mFantastic Frameworks and How to Avoid Them
34mDon't Let the Framework Stand in Your Way
47mQuick Start for Zend Framework 2
01h 07mRewriting 15-Year-Old Code
44mInterface Segregation for PHP