How does Laravel work exactly in your MVC model?

In summary, Laravel uses the routes to know which controller to call and which method. Then the controller responds back with a view. This means that the routes come into play before the controllers.

Adding to the comment of @PAGANA. From the moment you identified the concept of routes you can already realize that it is not exclusively an MVC, at least not pure. You can use it as such, but you can do a lot of other things

The concept of the model as such no longer exists, it allows you to generate the application structure you wish, only limited to your imagination.

Basically, the framework implements several design patterns: The Facade is used to call the services implemented by laravel through the ServiceProvider. Eloquent implements the ActiveRecord pattern Implements Fluid interfaces. Implements Template view with blade.

There are several videos and documentation where DDD with laravel is applied on large and evolving applications, something extremely ambitious for a language like php