Don't Be a Slave to Doctrine Anymore
summary
Doctrine is an ORM for mapping PHP object models to database schemas. The talk explains designing your architecture first and then adapting Doctrine to persist that model, showing how to use Doctrine’s flexibility to persist atypical or non-standard models and to avoid being constrained by the ORM.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 1:10Doctrine and alternatives
- 2:10Anemic model limits
- 5:22Domain Driven Design
- 7:29Separate domain and infra
- 8:13Builders and business rules
- 10:00Early data validation
- 12:13Unique IDs and Yo-Yo
- 14:20Value Objects and encapsulation
- 16:44Custom Doctrine types
- 19:53Value Objects and mapping
- 22:02Doctrine repositories issues
- 26:42Decouple repositories
- 28:52Doctrine collections
- 31:22Avoid OneToMany
- 33:14Cloning and final methods
- 34:37Doctrine and DDD
- 35:43Doctrine tips
- 37:53Entity dependencies
- 39:19Doctrine 3 and MariaDB
- 41:05YAML config deprecated
- 42:08Q&A
related talks
59mDoctrine ORM Good Practices and Tricks
21mLaravel Doctrine: A Data Mapper Approach
59mHow much database abstraction do I need?
48mObject modeling: Theory vs Practice. Round 1
28mOverly Attached ORM
25mCode decoupling from Symfony (and others frameworks)
02h 10mLet's play a game: No extends. Advanced OOP with Symfony 3
36mORM is an Offensive Anti-Pattern