Interesting video, thanks! However, a small note on Laravel's lack of help when deviating from MVC: I tend to build all my apps in Laravel using a DDD architecture. The features are there, just a bit hidden, or rather used mostly for libraries' development. You can specify where to load commands or views from, add middlewares to load specific service providers based on the routes, target controllers from any namespace in your routes files, or even create new routes' files that will be loaded in the RouteServiceProvider with their own middlewares. As I said before, the features are there, they're just not well documented. You can build a DDD app with Laravel, it just requires a bit of extra configuration
