Laravel Advanced: The Manager Pattern

[@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:
app(App\Support\Contracts\PaymentDriver::class) or inject into class method that will be resolved from the container.

[@medilies]

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

[@AhsanKhan89]

Great video. Thanks for this.

[@Данил-у9ы8б]

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

[@hugo-abdou]

thank you i was searching for this

[@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

[@Acadeaio]

yes that is pretty much OOP in a nutshell. At the end of the day, it is the implementation of interface methods that really counts

[@medilies]

The manager pattern feels more like a factory for me

[@codewithexperts]

create video on laravel intermediate to advanced

[@irfanullah9375]

❤ Interesting

[@irfanullah9375]

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

[@Acadeaio]

I have a lot more lessons in my website, would love to see you there!