I've been reviewing a Laravel project code and noticed the pattern in Controllers and decided to discuss with you.

My course "How to Structure Laravel 12 Projects" https://laraveldaily.com/course/laravel-projects-structure?mtm_campaign=youtube-260109-too-long-controllers 

Support the channel by checking out my products:
- My Laravel courses: https://laraveldaily.com/courses
- Filament examples: https://filamentexamples.com
- Livewire Kit Components: https://livewirekit.com

Other places to follow:
- My weekly Laravel newsletter: https://us11.campaign-archive.com/home/?u=a459401212599a54203d036ee&id=91c1337873
- My personal Twitter: https://twitter.com/povilaskorop

Laravel Daily

A code review examines Laravel controllers ranging from 400 to 1,355 lines, arguing they're too long. The author advocates for shorter controllers that delegate data processing to services, actions, or config files rather than containing private methods and hardcoded data. Examples show controllers with numerous private methods for data transformation, contrasted with cleaner patterns using dedicated service classes. The discussion centers on MVC principles where controllers should primarily handle request/response flow rather than business logic.

Laravel Controllers: How Many Lines are "Too Long"?