How to Structure Laravel Projects

IMPORTANT NOTICE: Since September 2022, I'm moving from this Teachable platform to my own LaravelDaily.com with this course and even more premium tutorials there. So, please subscribe to yearly/monthly membership there, this Teachable platform will not get new content anymore.

With any questions about the membership, email me [email protected]

The most often question I hear in Laravel is this:

“Where should I put this code logic?”

Basic Laravel is an MVC framework, it’s clear what should be in Model, View, and Controller. But what if you have custom logic for processing data before passing it to the view? Where should it be?

• In the same Controller method?
• Function in the Model?
• Separate class, like Service? Or Action?
• Put as a Job into the Queue?
• Or, maybe, a global helper function without any class?
• And the list goes on.

Of course, the correct answer is it depends. But depends on what?
This is what I’m gonna talk about in this course.

The goal is to discuss practical examples of structuring larger Laravel applications, various approaches, and patterns. We will analyze existing popular open-source projects and their structure.

Notice: this course won’t be about design patterns. So fancy keywords like Singleton, Factory, Adapter etc will be used only when appropriate.
What I will try to do is focus on the practical side: folders, classes and methods, and not on how that pattern actually is called in theory. In reality, every project is actually a mix of patterns, and developers don’t even know how they’re called.