Greg Skerman - 7 habits of a high performing team - Laracon AU 2023 

The only arguments _for_ repositories are straw man arguments: “But what if we change ORM? What if we change the database?” If you’re going to change your ORM, then you’re going to be writing code any way. Your “EloquentFooRepository” classes aren’t going to magically work if you decide to use say, Doctrine.

@@martinbean I don't think those are good arguments for using repositories. As I said, "using them everywhere is a bad idea". Repositories are useful for encapsulating complicated queries, re-using query logic between different classes, and hydrating objects outside of the eloquent/active record pattern (ie: domain objects in DDD). Using them as depicted in the video (e.g: simply wrapping all eloquent calls) is an obvious anti-pattern

@@coreymcmahon3969 Thanks for the feedback, and I take your point. I will say, its very difficult in a very small amount of time in a talk to cover all the nuance when you have 6 other topics you want to cover. For clarity, I wasn't calling for "never use repositories". I was calling for "don't just use them because you think there will be a benefit". Introduce them when (and precisely only when) theres a real need to make the tradeoffs. And the same goes for other patterns. Until theres an actual need, paint inside the lines and stay inside the lines as long as you possibly can. I tried to make this point towards the end of that section.