Software Design Patterns in Laravel 4
summary
Walks through concrete Laravel 4 examples and makes testable claims: the vendor code has 14 abstract classes out of 128; iterators lean on PHP’s builtins; event dispatch implements the observer pattern; alias loader acts like a singleton and the database manager is a multiton; facades route calls through the IoC to reusable instances, summarised as facade vs singleton; recommends service providers, repositories, factories and points to cache strategies (redis memcache files db memory) as live swapable implementations.
AI-written summary · about
chapters (23)
- 0:00Start
- 1:54Software Design Patterns
- 2:47The Patterns
- 3:19Notations
- 3:31Sub-class
- 3:48Class Instance
- 4:05Building Blocks
- 4:42Abstract Classes
- 5:59PHP's Iterator Interface
- 6:25Laravel's Iterators
- 6:40Observer
- 7:22Dispatcher
- 9:48Multiton
- 10:15Database Manager
- 11:40Input
- 12:03Route
- 12:20Response
- 13:18Facade vs Singleton
- 15:00BootstrapPresenter
- 15:51Repository
- 16:41Builder (aka Manager)
- 17:30Service Provider
- 18:00Strategy
related talks
38mLaravel Design Patterns
32mDesign Patterns and Packages for Excellent Laravel Backoffices
38mCrafting maintainable Laravel applications
02h 24mPractical design patterns in PHP (Part 1)
37mOrganizing Code in Laravel
44mAbusing Laravel for Fun and Profit
29mLuke Downing :: Lessons from the Laravel Framework
31mModern PHP development with Laravel 5.6