Agree. For most apps the repository design pattern is not necessary. We use the pattern for the project I’m currently working on so I wrote this post to understand the concept better and how to do a basic implementation in Laravel. Going forward I would not implement this for new apps but it is helpful to have an understanding of! One tricky part for me was using the interface and binding the interface within a provider. It took me a while to figure out. I appreciate your response.

Engineer, writer and community organizer. I built Employbl to help candidates get jobs in the Bay Area:

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store