Skip to main content

Black Friday 2025! Only until December 1st: coupon FRIDAY25 for 40% off Yearly/Lifetime membership!

Read more here

Conclusion: So Which Pattern(s) Should You Use?

Premium
3 min read

One of my goals in this course was to show you the options for which patterns you may use. I tried to limit them and show only the most practical ones, but maybe you're still confused about how to use all that information in your situation.

RECOGNIZE Patterns

By showing different examples, I wanted you to notice the patterns. This is the most common thing you need to do in your daily development life.

You would often need to take someone else's code and add features, not breaking the pattern from the original author.

Another example would be...

The Full Lesson is Only for Premium Members

Want to access all of our courses? (29 h 14 min)

You also get:

54 courses
Premium tutorials
Access to repositories
Private Discord
Get Premium for $129/year or $29/month

Already a member? Login here

Comments & Discussion

D
Davery ✓ Link copied!

Awesome course! It really opened my eyes to the design patterns used in Laravel. Now to dig in to the more complex patterns I need more experience with. Thank you!

PC
Pavel Chebukin ✓ Link copied!

Thanks a lot! It's very good in addition to gurufactoring book, as real-world examples tour with comments.

M
Modestas ✓ Link copied!

One thing I’m missing is the DTO (Data Transfer Object) pattern. Just like the Repository pattern, which isn’t as popular or widely used these days, DTOs also seem less essential in modern development. However, I’d still like to see some practical examples of how the DTO pattern can be applied, especially in Laravel.

M
Modestas ✓ Link copied!

The DTO itself is not quite a pattern. It's more of a way to transfer data between methods. So this wouldn't fit into the design pattern workflow at all. But we do have an older tutorial on DTOs here: https://laraveldaily.com/post/value-objects-and-data-transfer-objects-in-laravel

As for repositories - we are strong believers that Repository pattern is not worth pursuing in Laravel. There is more negatives in using it with Laravel than there is benefits. Especially if you are just starting and heard the phrase "repositories are required in modern applications".

M
Modestas ✓ Link copied!

You're absolutely right—DTOs are more about structuring data transfer rather than being a design pattern. Thanks for sharing the tutorial! As for repositories, I completely agree. In Laravel, they often lead to unnecessary code duplication since Eloquent already provides a great abstraction. In most cases, adding a repository layer just adds complexity without real benefits.

We'd Love Your Feedback

Tell us what you like or what we can improve

Feel free to share anything you like or dislike about this page or the platform in general.