https://twitter.com/taylorotwell/status/634384068990267392
Laravel lets you create your own architecture. MVC is too generic.
Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.
Hi @JeffreyWay
I'm taking a software design course this semester, and I choose to implement my project using Laravel. Now, I'm working on my system architecture.
When I read how the request is handled in Laravel I saw that there is middlewares, service container, and service providers not only controllers.
So, is Laravel an actual MVC architecture? Is there a useful resource about Laravel architecture?
UPDATE: Based on @DarkRoast and @crnkovic answers, Laravel is not MVC (Specifically not only MVC) , and I can organize my system in any structure that I want.
MVC is just a tip of the iceberg. Laravel allows you to create apps using MVC pattern, but the framework itself is much more complicated.
Laravel 4 had models, controllers and views folder, but 5 does not because it's not only MVC (e.g. controllers are a part of the HTTP layer -- containing Middleware, Requests and Responses, etc). That said, you can see there are much more layers, not only M V and C.
But, the application you build is mostly wrapped around MVC pattern because most of the time, you don't even need anything below the surface.
Organize and structure apps in the way that solves your problems.
Please or to participate in this conversation.