Modelling business requirements with Eloquent
summary
Eloquent and Laravel are the tools shown and the claim is concrete: move business terms into domain methods like start/submit domain methods, stop calling save everywhere, and encapsulate pivot logic by making Assignment a first-class model that handles score and abstain state. Examples include attach/score/abstain implementations, raising events and dispatching side effects with events and command handlers, and a migration path off ActiveRecord by isolating persistence behind these domain APIs.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:50INTRODUCTION
- 4:39LET'S DEAL WITH THE UGLY
- 5:45WHAT WE'LL COVER
- 7:15SAMPLE CASE STUDY
- 11:24NEW REQUIREMENT
- 15:17RECAP
- 24:14DOMAIN-DRIVEN ELOQUENT
related talks
21mUsing the Repository Pattern with Eloquent for Code That Lasts
40mEngineering Complex Applications with Laravel 4
21mLaravel Doctrine: A Data Mapper Approach
32mFull stack architecture
01h 03mUnbreakable Domain Models
20mhow to make the management of a league system less traumatic
21mSoftware Design Patterns in Laravel 4
35mBuild Complex Domains in Rails