Advanced Laravel: Avoid unified data models
summary
Argues against one giant User model and shows a working Laravel conference app that splits responsibilities into feature-scoped Eloquent models (auth, speaker, organizer, submitted_talks) and wires them with Laravel events; submit action emits a talk submitted event and listeners map that payload into a separate approval table. Demonstrates actual migrations, controllers, event classes and listeners, builds four features end-to-end, and shows the approach reduces coupling and lets features be removed or changed without breaking the whole system — app fully functioning with source available.
AI-written summary · about
chapters (20)
- 0:00Start
- 2:49Conceptual Model
- 4:46Relational Data Model
- 5:29Hierarchical Data Model
- 6:41Database Tables
- 6:58Object Model
- 7:30Eloquent is ActiveRecord
- 7:59Eloquent is Relational
- 8:18Schema Leakage
- 14:21Mappings are Boundaries
- 14:43Isolate Leakage at ORM Model
- 19:44Objects have Fields
- 20:01Objects have Methods
- 21:34How does it work?
- 22:26Scope Reduction through Boundaries
- 27:16Consequences
- 28:49Auth Implementation
- 30:02Feature Summary
- 30:28Talk Submission Implementation
- 33:13Talk Approval Implementation
related talks
29mLuke Downing :: Lessons from the Laravel Framework
21mLaravel Doctrine: A Data Mapper Approach
21mSoftware Design Patterns in Laravel 4
31mModern PHP development with Laravel 5.6
38mCrafting maintainable Laravel applications
32mDesign Patterns and Packages for Excellent Laravel Backoffices
36mSimplifying Complexity with Federated Applications
37mLife Beyond Microservices: Modular Monoliths in Laravel