Laravel 6 Advanced - e7 - Repository Pattern
HTML-код
- Опубликовано: 8 сен 2019
- 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.com
DigitalOcean Referral
m.do.co/c/7dce5364ef4d
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?
![Laravel урок №25: [ Что такое Репозиторий? #1 ]](/img/1.gif)
this is crazy dude. hope you have good health to create more videos. I learn a lot from your videos.
Dude, that map->format(); is genius, Wow
Also I've never know that we can ->diffForHumans() from carbon, thanks so much
where were you, finally I found someone that knows pure implementation and architecture.
Man, I watch A LOT of educational videos on coding (php, js, laravel, vue) and you are the best.
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!
These advanced series are very helpful. Thanks!
Happy to hear that. More advanced topics are much more time consuming in preparation leading up to recording the lesson.
@@CodersTape Thanks for your work Victor, what about another Udemy course applying those advanced concept ?
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.
your practical explanation is phenomenal. Keep up the good work please, people like us depend on you.
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.
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.
Just totally love all your tutorials. Keep it up.
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!
Interface implementation was my best part, loved it!
Crazy good content, thanks a lot for posting this. The quality of this video is unreal. God bless you man!!
The best coding channel out there. I hope you post more videos as you used to.
Very helpful , I was waiting for it thank you so much, really appreciate all the valuable content you provided thanks again!
That was awesome , thanks , these Advanced video series are awesome .
An extremely useful lesson, thank you, Victor!
Thank you, bro!!! You are awesome! I learnt everything I'm confused. Thank you for your lessons. Sincerely, Sanjarbek from Uzbekistan.
This is why i love Laravel. Thanks for your good videos :)
I never not like every single video i watched from this dude. Thanks a lot bro.
If I could to press "Like" twice, I would do it! Awesome tutorial as always.
Your videos are simply the best, thank you
Learning more advanced things in this advanced laravel series, out of the box :) .... Need a tutorial on Service Pattern implementation
I will definitely implement the format function, I feel like I've been repeating myself a lot on database queries. Thanks!
Experiment Fractal
Thank u so much, we need people like you in this world
Excellent explanation, grasped it immediately.
100% Perfect !!
Thank You very Much Bro !! :D
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!
I love your tone and the content here
Thanks for this great episode!
Mannn i really love this course!!!
awesome , can you make more videos like this ? implementing design patterns and advanced php and laravel technics are awesome . Thanks again
Very well explained. Useful content.
that's greate, greate series, greate demonstrations and easy to understand, thanks man :))))
I was smiling while watching your video and thinks how a person could be so good at ♥️
Thank you
thanks for creating such amazing video , i really love the way u clear concept in depth .
you're the best ever in explaining leravel
Great great video please make more advance video. You are really professional programmer.
This is very useful. I learnt a lot. Thanks for the video.
WONDERFUL DUDE! KEEP GOING! U'RE A MAN!
The BEST as always!
Thanks a lot. Finally I understand repositories :))
Another good one! Keep it up bro! God bless you
My god dude! thanks so much!! this video clarified me a lot of things. Love ur channel and content! cheers
This is a great ep. Thx for showing us this. Would you make a video on caching?
Great explanation about repository pattern :-)
just a awesome video bro!! thanks a lot bro
Cool, unfortunately beginners take Repository as granted, glad that you pointed out that it is meant for larger apps!
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.
👏🏼👏🏼👏🏼
Thanks
well, you are still not, because repo pattern is not needed when using laravel
it is a very nice course, thanks!
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.
Collection()->map->formatCallback()? and you dont kidding? Freakin awesome! That save me at least 1000 rows of code! Awesome! Thank you so much!
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.
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
So what are we supposed to use instead of repos?
Thank you very much for this tutorial
Thank you !! very clear !
Outstanding, thank u!
Thanks so much for this tutorial
Wow! This is amazing! You are a god!
Very good explanation 🎉🎉
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.
Absolutely.
Quick note. You bind interfaces in register() method of the service provider
very nice, thanks!!
This is the best quality content coding pattern
wow! thanks a lot man!
I enjoyed it. thanks
Thank you so much!
Thank you! 😄
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
Thanks so much , just keep going :)
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.
Outstanding
Nice video. I really learn a lot. I wonder why people gave this a thumb down
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.
May I ask where they are going to be called when formatting? should it be on the controller? or on the repository?
Thank you 👍
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
Thanks
@@CodersTape have you big man?
mind blowing video I have ever seen in the youtube
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.
you are awesome dude
Thanks! Happy to help
Tnx alot.. so helpfull
I find formatting with Resources is much more flexible
out of the box :)
brilliant !
using request() in repository very nice
i hope i've seen your channel before my project... life shouldve been way easier
Great work...please go ahead. When is the next one e8 ?
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.
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?.
Amazing
Hmm. . . Im still learning thanks bro...
hi there, it's been long that you haven't published a video, I love your content, please start making videos again :)
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.
dude come back and create amazing tutorials for us.
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.
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
bro it's so cool
You are perfect 👌
Thanks! Happy to help
Would love a video on Lazy Collections 👍
That’s next!
I am wondering that in this case, what is correct when we put the interface’s binding in ‘boot’ or ‘register’ function?
Thank's
Thanks for sharing. This repostories like Helper, are we use without construct
Like "use App/Repostories/TestRepostory"
I was use like this, some 5.x version in laravel