Category: Laravel, Laravel, PHP, PHP

In this article I talk about the Repository Pattern and how we implemented it in our application to solve a scalability problem. The Repository Pattern is one of the most disccussed patterns due to a lot of conflicts with ORMs.

We discuss this topic in detail, explaining why and how we implemented it in our backend. The most obvious reason of why an abstraction layer exists in almost any application, is to drastically reduce code duplication.

I would start talking about some bogus problems, in order to clarify immediately when it is “not” necessary to introduce the Repository layer.
Newsletter

Get the latest Laravel/PHP jobs, events and curated articles straight to your inbox, once a week

Glimpse streamlines Laravel development by seamlessly deploying GitHub pull requests to preview environments with the help of Laravel Forge. Glimpse streamlines Laravel development by seamlessly deploying GitHub pull requests to preview environments with the help of Laravel Forge.
Fathom Analytics | Fast, simple and privacy-focused website analytics. Fathom Analytics | Fast, simple and privacy-focused website analytics.
Shirts painstakingly handcrafted by under-caffeinated developers. Shirts painstakingly handcrafted by under-caffeinated developers.
Community Partners