Ep18 - Repository Pattern | Laravel API Server

There is a software design pattern called "Repository". It is basically a middle layer between the database and our app. Let's take a deeper look at it in this lesson.

------------

Source code for this lesson:



** Affiliated links

Earn passive income from crypto while you sleep! Get started on Nexo today! Up to 12% annual interest. Get $10 USD reward if you use my referral link below.

Use the legendary Git GUI for FREE! You are seriously missing out if you are not using it.

Beautiful designs created instantly to wow your social networks!

A simple and scalable cloud hosting platform for all developer needs.

Get started on Crypto today. Gets 10% off of all crypto trading fee if you use my referral link below.

Songs Used:

Outro Music:

[mark]

Shouldn't the repository be accessible through a service class rather than directly on the controller?

[phojie]

That is not purpose of repository. Use services instead

[debjit]

Why use DB: Transaction? why not use Form Request? Why not use Response to return the request?

[Engazan]

so "data_get" is same as "$a['aaa'] ?? 'b'" so its useless am i right ?

[sanal]

Hello, thank you so much for this excellent series. I wonder why you used abstract class in the repository instead of interface?