Laravel Advanced: The Manager Pattern

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



** Affiliated links
Email marketing is made simple! Affordable and powerful! Build your audience starting today!

Earn passive income from crypto while you sleep! Get started on Nexo today! Up to 16% annual interest. Get rewards if you use my referral link below.

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

Get started on Crypto today. Use my referral link below to get 10% off of all crypto trading fees.

Outro Music:

[medilies]

Thank you for the unique content. I often inject the mentioned managers into my classes instead of using the facades.

[devhammed]

Instead of creating a "lib" folder, I usually follow the following folder structure:

app
---- Support
Contracts - The interfaces (e.g PaymentDriver)
Managers - The managers (e.g PaymentManager)
Services - The implementations (e.g StripePaymentDriver)

And then the users can do something like:

or inject into class method that will be resolved from the container.

[Данил-уыб]

It seems to me that this is just one of the implementations of an abstract factory

[RudolfBrudersChannel]

I have a feeling that there are multiple patterns with different names doing the same thing. Like this manager pattern is the same as strategy pattern and in the end repository pattern (but deals only with data) is that right in you opinion? It all comes down to code against interface

[codewithexperts]

create video on laravel intermediate to advanced

[irfanullah]

Please sir make at least one video in week for your viewers