Laravel 6 Advanced - e7 - Repository Pattern

The Repository Pattern is a common refactor that you may encounter in large Laravel applications. While it is not ideal for small to medium projects, it's a perfect solution for those applications that need an abstraction of the data layer.
For the best experience, follow along in our interactive school at www.coderstape...
DigitalOcean Referral
m.do.co/c/7dce...
Hit us up on Twitter with any questions or comments @codertape ( / coderstape )
About This Course
Ready to level up your Laravel skills? This series is for you, follow along as we uncover the advanced Laravel features that actually make Laravel the most popular php framework. We'll have lot of tips and tricks along the way. Are you ready?

[@morleytechtv7749]

this is crazy dude. hope you have good health to create more videos. I learn a lot from your videos.

[@andynguyen8124]

Dude, that map->format(); is genius, Wow Also I've never know that we can ->diffForHumans() from carbon, thanks so much

[@kasmanialisaad]

These advanced series are very helpful. Thanks!

[@CodersTape]

Happy to hear that. More advanced topics are much more time consuming in preparation leading up to recording the lesson.

[@julienSibille]

@@CodersTape Thanks for your work Victor, what about another Udemy course applying those advanced concept ?

[@priteshshinde6779]

We understand that it is more time consuming, but you know you've got 1 more subscriber just now (me). I'm sure you'll get alot more subscribers until this series end, but please make more videos.

[@abunooh9005]

I never comment on anything, but this series is just too helpful. You are my new Laravel teacher. Keep it up and thank you very much. You are awesome!

[@victorwillhuber]

Man, I watch A LOT of educational videos on coding (php, js, laravel, vue) and you are the best.

[@agent_mo]

your practical explanation is phenomenal. Keep up the good work please, people like us depend on you.

[@phentube2345]

where were you, finally I found someone that knows pure implementation and architecture.

[@ahmadmayahi]

The repository should only be used to reterive the data. It's a common mistake that some developers use repositories for storing/updating/deleting, but it’s not meant to be like that. If you need to store/update/delete then you have to have a persistent layer. I think Doctrine did the best implementaion of repositories.

[@dr.adam.nielsen]

In literature you find that the main purpose of repositories is to be a layer between your data mapping and the business logic. Its totally fine to store/update/delete date there. See stackoverflow.com/questions/57340681/should-we-save-update-models-in-repository-pattern

[@Wane-maxx]

So what are we supposed to use instead of repos?

[@ProgrammingwithPeter]

Cool, unfortunately beginners take Repository as granted, glad that you pointed out that it is meant for larger apps!

[@AirMalta89]

This course is amazing. Not the usual blah-blah most good laravel devs already know. But really insightful, solving real-life problems where you were thinking as a dev, there should be a nicer solution for this!

[@mohammedmahmoud1182]

The best coding channel out there. I hope you post more videos as you used to.

[@wanamra899]

I never not like every single video i watched from this dude. Thanks a lot bro.

[@Yuri-sf5mx]

Watched this video to fresh up my memory on repositories and honestly you make great videos and your explanation is to the point. Love your style. On the subject though i do find that the only reason you should use repositories is when you expect to swap out your database for something else. Other than that i stick with model query scopes for the repetitive query's (powerfull for their chainability) and use resources to format them. Even on very large projects. You could still use repositories in combination with these, but as said, the only added value is data driver independency. *Edit* Looks like this has been said a few times. Either way, it boils down to project requirements and personal favor. There is no "right" way.

[@CodersTape]

Absolutely.

[@utshabroy]

Thanks you for this video. I learned a lot. However, I read some blog where the Repository is connected with the ServiceLayer. If I'm right then can you please make a video on how Repository and ServiceLayer works together on big projects. Thank you again 😊 you are the best Laravel tutor.

[@Stoney_Eagle]

I will definitely implement the format function, I feel like I've been repeating myself a lot on database queries. Thanks!

[@brunofunnie]

Experiment Fractal

[@josebriceno7578]

Crazy good content, thanks a lot for posting this. The quality of this video is unreal. God bless you man!!

[@ammaralhomyqani9079]

Thank u so much, we need people like you in this world

[@MarcoAZeballosS]

It's the first time I get to clearly understand Repositories. I cannot pass to the next video without congratulating you and thanking you for such amazing video/explanation. 👏🏼👏🏼👏🏼

[@CodersTape]

Thanks

[@Wane-maxx]

well, you are still not, because repo pattern is not needed when using laravel

[@MustafaBirsoz]

I love your tone and the content here

[@yuchenglong672]

I think for those who don't potentially change their projects databases, a cleaner way is to implement a eloquent based repository design pattern, that works specifically with laravel eloquent, and just so much cleaner and readable. For a large projects which may be deployed with different types of dbs, a middle layer like the repository interface design pattern is almost like a must go-to idea.

[@aristideherve5748]

You are incredible ! I asked for a video on it in your last video and you did it. Everything is clear ans precise. God bless you!

[@ahmadmayahi]

12:19 You can avoid mixing transformers into repositories by using an external transformer. In this case, the fractal package would be amazing to use.

[@KuroUsagi1010]

May I ask where they are going to be called when formatting? should it be on the controller? or on the repository?

[@yurabobrov6717]

If I could to press "Like" twice, I would do it! Awesome tutorial as always.

[@milantarami]

Learning more advanced things in this advanced laravel series, out of the box :) .... Need a tutorial on Service Pattern implementation

[@shaheerarain50]

I was smiling while watching your video and thinks how a person could be so good at ♥️ Thank you

[@paolopalubs64]

Very informative! I've been using using model repositories for a long time now, and this is a good tutorial for those who haven't tried it yet. This is useful specially when doing reports.

[@oghenerukevwekofi7976]

I think repositories are also beneficial for testing. When you have the data layer coded against an interface like this, it becomes easier to mock it while testing. Depending on your needs, I think you might want to be able to separate tests that will reach the database from tests that just see if your basic functionality is working or not.

[@nullpadshot]

Collection()->map->formatCallback()? and you dont kidding? Freakin awesome! That save me at least 1000 rows of code! Awesome! Thank you so much!

[@MrAlaa3344]

you're the best ever in explaining leravel

[@fabianleon1744]

Thank you very much for these videos 🙌. I have read many times about the repository pattern, but this is by far the best explanation I have found.

[@ssjuma]

Interface implementation was my best part, loved it!

[@peymanGhaderkurehpaz]

awesome , can you make more videos like this ? implementing design patterns and advanced php and laravel technics are awesome . Thanks again

[@rahulshimpi8914]

Great great video please make more advance video. You are really professional programmer.

[@TUTORIALSUZ]

Thank you, bro!!! You are awesome! I learnt everything I'm confused. Thank you for your lessons. Sincerely, Sanjarbek from Uzbekistan.

[@serhiicho]

Quick note. You bind interfaces in register() method of the service provider

[@tonviet712]

This map->format() blow my mind. That’s incredible video. But I still have some confusions: I knew about this pattern, but still don’t understand why this is necessary. Does it put all of logic to get data from Model to Repository? What pros and cons when put all logic in Model instead of Repository? Thank in advance

[@CodersTape]

truthfully, I think it's a design decision more than anything. I particularly like heavy models and don't use repository patterns. One use case I can understand is when you are managing several different data sources and need to access them equally. Example might be news, let's pretend you are receiving news feeds, one is coming as an RSS feed, another is content written in-house and maybe 3-4 different sources. Repository will make the consolidation easier because they can be treated differently but accessed with the same API.

[@tonviet712]

Coder's Tape You are my new fav teacher. Great explanation !!! Thanksssss

[@CodersTape]

@@tonviet712 Thanks!

[@adaamgbede283]

Nice video. I really learn a lot. I wonder why people gave this a thumb down

[@hassanalthaf8561]

I would honestly keep that format method within the Repository, as when you're writing a new concrete implementation of the repository, you might miss out on that specific business rule.

[@Brianle180]

Just totally love all your tutorials. Keep it up.

[@dilipdev8699]

Really amazing!. What about next point after implementation the interface?. Even without the interface we can do the same things. Then what's the purpose of the interface here?.

[@Darren502]

This is a great ep. Thx for showing us this. Would you make a video on caching?

[@personal1872]

hi there, it's been long that you haven't published a video, I love your content, please start making videos again :)

[@sardinas3675]

This is fr**king awesome my friend! I hope that someday or in the future that you will create a video on SOLID pattern in laravel. Btw You are the best

[@CodersTape]

Thanks

[@codewithtee]

@@CodersTape have you big man?

[@SunilparajuliKenshin]

This is the best quality content coding pattern

[@loremipsum574]

Please create a SOLID pattern tutorial. It would help a lot of beginners like me.

[@tarikhagustia939]

up

[@CodersTape]

Would you say it would be better to exclude Laravel from it and keep it simple with plan PHP?

[@loremipsum574]

@@CodersTape I mean SOLID pattern in laravel. If you search on the web there's no such thing as SOLID pattern tutorial it would be you the first one will do it. There's a solid pattern tutorial but not complete.

[@Eugene.g]

@@CodersTape SOLID principles and design patterns are pretty abstract, so real life examples with refactoring in Laravel would be awsome to see. I think youtube lacks this type of advanced content on how to structure a Laravel app and how to use patterns

[@Yuri-sf5mx]

This is something i hear a lot from beginners and had issues with myself when i started using Laravel. Laravel is great because it's all very "loosely", but as a beginner you have no clue how to organize files/namespaces, how to name classes, how to write functions, how to separate things, ... But i don't think a solid "all use case" pattern is possible because not all project will fit this pattern. A pattern is required, but should be on project level and defined in the abstract layout of your project. Before the first line of code is written the pattern should be established.

[@xdEdgarBest]

Your videos are simply the best, thank you

[@Moonlit_Loops88]

thanks for creating such amazing video , i really love the way u clear concept in depth .

[@vrabecm]

Dude, nice tutorials. Only 1 cent from me: I think repositories should be used entirely for one purpose - retrieving data. Update, store and delete functions should be found in the model or a Service.

[@CodersTape]

I’ve seen it both ways in the wild. And I see both points of views.

[@vrabecm]

@@CodersTape Yeah, I agree, it's a personal opinion. Anyway, keep up with the videos, they are absolutely amazing.

[@ahmedhamza9277]

that's greate, greate series, greate demonstrations and easy to understand, thanks man :))))

[@colonelvector]

Excellent explanation, grasped it immediately.

[@mori181186]

This is why i love Laravel. Thanks for your good videos :)

[@Laflamablanca969]

I find formatting with Resources is much more flexible

[@peymanGhaderkurehpaz]

That was awesome , thanks , these Advanced video series are awesome .

[@ayazahamed8254]

Very well explained. Useful content.

[@anoopsankar7726]

This is very useful. I learnt a lot. Thanks for the video.

[@phoe7ix]

An extremely useful lesson, thank you, Victor!

[@2012potter]

Awesome. You could've used Eloquent resources instead of format() right?

[@KistlakRajapakshaSevenNet]

100% Perfect !! Thank You very Much Bro !! :D

[@KoganeNoYubi]

great stuff, but how would you combine repositories with API resources?

[@melomancheto2761]

I do not agree on the part of format and transform. You can't choose format, formating is for dates for examples. What we are doing with this data is transforming it . But the tutorial and not only this one, all of them are awesome!! Keep up the great content. Something else is that the request has nothing to do with the Repository. The repo is just a middle layer between the database and the Controller (I use this example to be more close to Laravel). We need to pass all the data we need as params and never pass the Request outside of the Controller.

[@limuelmendoza5356]

i hope i've seen your channel before my project... life shouldve been way easier

[@carlosmillanmazzucco1766]

My god dude! thanks so much!! this video clarified me a lot of things. Love ur channel and content! cheers

[@maharagab5107]

Very helpful , I was waiting for it thank you so much, really appreciate all the valuable content you provided thanks again!

[@RichardOpokuEngineer]

I have implemented the repository pattern before and this has been really helpful to add to my understanding. However, some folks somewhere on the internet claim that it should rather be a service layer and not repositories. I recently had to refactor one source code to reflect *services* instead of the *repositories* I had already implemented. I need help understanding these further.

[@CodersTape]

The service layer is the abstraction of the controller where the repository is the abstraction of the model. Typically you inject a repository into the service layer so you would still need both and it's just yet another abstraction layer between the view and the controller. So the order would be Controller > Service > Repository > Model is it better? I can't agree that it is in most cases. I think it's just hiding away bad code design but I am open to seeing some code samples. :)

[@truthseeker2171]

@@CodersTape Wow, that's quite interesting. I am implementing a payment gateway (API) with an ecommerce app where I would like to have a lot of the business logic in the services and then manipulate the data using Repositories. But while following the above structure, *Controller > Service > Repository > Model* where will FormRequests come in for validation?

[@TolvirRam]

Thanks a lot. Finally I understand repositories :))

[@THEShAdOwHFV]

Min 21:00 For those that can't load the provider when registering it in app.php file (test the provider with dd("plainText")) You can do: php artisan config:clear php artisan clear-compiled composer dump-autoload If composer is failing, just delete the "dd("test")" in your provider

[@mubashirali5687]

Great explanation about repository pattern :-)

[@amirkaftari5188]

dude come back and create amazing tutorials for us.

[@kevteg7305]

I think it better to use Scope Modele to manage that in pure laravel way.

[@CodersTape]

Both techniques have a time and place. It’s good to know both.

[@rolanddecasa4438]

Another good one! Keep it up bro! God bless you

[@mohd.aadilads3889]

Very good explanation 🎉🎉

[@shirjeelkhan]

Great work...please go ahead. When is the next one e8 ?

[@joshbarros1995]

Nice video! Do you intend to teach how to apply Services, TDD and Domain Driven Design on Laravel 8?

[@djanthony6662]

I think some of these concepts could be done by using Query Scope for readability if you are using Eloquent: $customers = Customer::isActive()->orderBy('name', 'asc')->withUser()->get(); then pass that to API resource class for formatting: use App\Http\Resources\CustomerResource; return new CustomerResource::collection($customers);

[@SamehNabilAhmed]

you are awesome dude

[@CodersTape]

Thanks! Happy to help

[@vimkndll4171]

mind blowing video I have ever seen in the youtube

[@asdf7972]

Mannn i really love this course!!!

[@JordiViure]

Great! But.. this actions implemented in the repository can not be implemented inside the model? What s the difference? Thanks!!

[@CodersTape]

The difference is that if you don’t want to use a database or Eloquent, you can’t use the model. You can write a flat file implementation for example or use Redis or anything else you can think of to provide the data, not just a traditional database. It can even be provided by an API.

[@golubevblog2279]

WONDERFUL DUDE! KEEP GOING! U'RE A MAN!

[@haki3018]

using request() in repository very nice

[@mohamedtalaat8945]

Thanks for this great episode!

[@MrNescafe87]

thanks for your explaination for this pattern and it helps so much but i actually have some questions. i know the reason for using the repository pattern but isn't this is why we use services classes ? For example " Making a UserService Class and inject it in controller and retrieve the users like : $this->userService->getAll() ? And why using the map method to format the response and not use the resources ?

[@tsalVlog]

I had no idea PHP had real interfaces now. It's been a while...

[@juanmanuelmazariegos4598]

Hello, amazing video, sorry, where going the logic?

[@robert5488]

Thanks very much for these videos! They are brilliant, concise and very clear. Better than Laracasts. Would love to see more videos on design patterns and clean code fundamentals.

[@ristekostadinov2820]

If more than one class implements the CustomerRepository then in boot method of the provider we should register both of them (the interface with the first class and the interface with the second class) ? For example you can implement the interface with 2 classes one with pure eloquent ORM and second class with query builder

[@Kortess]

Hi, are there any plans for Docker lessons?

[@Brianle180]

I am wondering that in this case, what is correct when we put the interface’s binding in ‘boot’ or ‘register’ function?

[@mohaimenkhalid3844]

just a awesome video bro!! thanks a lot bro

[@SimpleLangSolution]

Wow! This is amazing! You are a god!

[@NathanBudd]

Would love a video on Lazy Collections 👍

[@CodersTape]

That’s next!

[@zohaibtariq-software-engineer]

after adding RepositoriesServiceProvider to config\app you must need to run php artisan config:cache after this it will work.

[@manzadey]

Eloquent is already a repository isn't it? Does it make sense to create another repository above the repository?

[@carlosolivas2878]

it is a very nice course, thanks!

[@Paltibenlaish]

question> why dont use the model to write directly the methods there??? why extra layer of abstraction?

[@adrianhojny2920]

Show it to guys from India, who take all logic to controllers :')

[@jeck0898]

Thanks so much for this tutorial

[@dgloria]

What's the difference between this and the resources? And how to handle more than one table?

[@AlexandrStiopkin]

Nice video but it is a bad idea to use request inside of a repository because repository it is a part of a domain layout.

[@thekiharani]

Cool stuff, but I got a query: I there a way you can paginate the records either before or after you transform?