I have seen almost all the design pattern videos on this channel. They are to the point, explain concepts with relevant examples. Kudos!

I seen so many youTuber to learn this pattern in 35 or 30 mint long videos.the funny thing they did not teach me in 35 mint which you just did in 7 mints. superb

God bless you. I was trying to read my textbook for all of these strategies and was ready to throw my laptop at the wall. This is simple to understand even for beginners. Thank you!!

Really amazing content with real life examples. Good work (y) . Subscribed! :)

This channel is an amazing complement for the book design patterns, really great to see the patterns explained in video after reading about the details in the book, thank you

@suleymanaghamoglanli4439

2 ай бұрын

I do the opposite, first view the videos and then read the book you mentioned.

Clear, simple explanation, great video! I would also add that this pattern not only applies the Single Responsibility and Open-Closed principles, but also the Dependency Inversion. By using this pattern you avoid that your high level modules (in this case, PaymentService) have dependencies with your low level modules (CreditCard implementation, Paypal implementation, Bank transfer implementation, etc)

Very helpful thank you!!

Its so unfortunate that I found your channel only now. Top notch explanation!

I really like how you break this down.

amazing videos! great explanation, thank you very much.

Great explanation! I've seen a few vids on the strategy pattern but this one definetly stands out :)

@geekific

2 жыл бұрын

Thanks a lot! Glad you found it helpful :)

Thanks for those very clear explainations 🙏

Thanks for this video I didn't understand it at my university but now I understood all. Thanks 😊 .

Amazing Explaination Thank you

This is really the best explanation.

Great explanatio, Thank you.

thanks alot for this video i learnt this example from ur video and same question is asked in interview n they are impressed for it 🎉 thanks alot for the video

Fenomenal, as the other videos in the series. The fact that you gave context, explained differences and showed up an example in only 7:26 mins says a lot of your experience. Keep it up! You bring so much value into the community 🚀

@geekific

2 жыл бұрын

Thanks a lot for your kind words man! Glad you enjoyed it :)

Very clear and pragmatic comparison with state pattern. May be I will spend a week to go through all your tutorials and take notes and then will attend interviews. Would like to know your profile.

@geekific

2 жыл бұрын

Happy to read it! Best of luck man :) If you need help let me know via the youtube mail!

Good Explain !

The interviewer was good. From low to high. ❤

Wow great video thanks, what are books or online resources that bridge the gap from “beginner” knowledge such creating a class, for loops , etc .. To best practices and design patterns ?

@geekific

2 ай бұрын

Thank you! I don't have a single resource, before each video I try to look-up as much references as possible so that nothing is missed. So, our channel might be a good answer to your question I guess :P

Thanks for such an amazing content. Could you please let me know how did you design the intro of this video ? Which app did you use ? Where can I also get such amazing videos for an intro ? Thanks in advance!

@geekific

4 ай бұрын

Glad I could help! I auto-generated it online, but planning to change it soon. Can't remember the website name anymore xD

Changing the payment type at runtime, this is an example of Dependency Injection. Right?

3:47 - in the main function, you have to set the payment strategy anyways based on the user's choice of payment method. So you will have to have some logic (conditions) around choosing the strategy like you had in the initial code (if (creditCardPayment) { ... } else if (paypalPayment) { ... } ...). How would you elegantly deal with this?

@geekific

8 ай бұрын

Depends on the context. If we take this particular example, and try to apply it on an order page of some website where you have icons for credit card, PayPal etc. and upon clicking on each icon the correct payment is selected. Then in the initial impl both icons would forward to the same nested-ifs, whereas with Strategy you won't have if's anymore as each icon will be tied to a strategy... Hope this answers your question. Cheers!

Phenomenal!!!

@geekific

2 жыл бұрын

Glad you liked it :)

Thank you for the beautiful video. I have a question if you do not mind. In the CONTEXT class, instead of making a field holding the strategy and implementing a set method to update the strategy ... could we just pass the strategy to the payment method as a parameter? Like: processOrder(PaymentStrategy ps){ ps.collrctio..... } What is the difference between the 2 implementations, is it wrong to do it this way ?

@geekific

Жыл бұрын

Glad you like them! There is nothing wrong with the approach you can do that, however, if you have multiple methods depending on this strategy (and not just one like in the example we have) you will have to pass it to every single one of them. On the other hand, if you pass it via a constructor or create a setter for it, you'll just need it once, that's is why I went with this approach, but both are fine :)

@allopiccipolla8061

Жыл бұрын

@@geekific perfect, thank you :)

3:46 your main class uses a setStrategy() method but there isn't this method on PaymentService class

@SauliusKulakauskas

2 ай бұрын

There is a lombok @Setter annotation for the class which generates the setters for all of the PaymentService class fields :)

My confusion isn't with the state pattern. Rather, I am trying to understand how the strategy pattern is different from the factory pattern (different classes sharing an interface are created) or dependency injection (client creates object and passes it to the context). For the former, as a creational pattern perhaps the focus would be on the creation of subclasses of the PaymentStrategy itself, rather than its behavior? For the latter case, strategy looks exactly like a setter injection. But then dependency injection isn't a design pattern, right?

@geekific

Жыл бұрын

Hello, feel free to check our dependency injection video here: kzread.info/dash/bejne/eXWItbqmZ7qnqLg.html. And to answer your question, the factory pattern is focused on the creation of the object, not its behavior. You can have a factory that spawns 10 different sub-products, but all of these products share the same exact functionality with the same exact underlying implementation (with creational patterns we answer WHAT is the object to create going to be). However, Strategy, as its name implies focuses on HOW the object is going to behave, so I can have the same exact object, but given a certain strategy it will act in a different way then when provided with another strategy, even if both lead to the same result, but the underlying behavior is be different. Hope this answers it! Cheers!

@yashwantptl7

11 ай бұрын

came here looking for the exact comment

where is the setStrategy method defined in the PaymentService ???

@geekific

3 ай бұрын

Oops!

But even if we use strategy design pattern we still have to decide what strategy to use. In your example you say that we need to "find" the right strategy at runtime, but isn't it it the same if else statement at the end which we were trying to avoid?

@geekific

2 ай бұрын

Depends on the front-end solution. Take a very simple example, a page with 3 buttons, each button will launch a different strategy :) But from back-end perspective u r covered! Hope this answers it!

@zheenbekakimzhanov8969

2 ай бұрын

@geekific oh, I didn't actually expect a response 😅 Anyway, after reading your response now I have another question in mind. I get what you mean, and basically you say that every possible outcome should have their own separate functions or api endpoints and which one to use is up to frontend implementation. But I'm just stuck with the analogy you showed in the video where in the first place you showed if else statements and you said this can be avoided via the strategy pattern. But by using strategy pattern we did not "solve" the if else statement problem and the initial code was completely removed. We for sure made the code more modular and just said well now it is someone else's problem to make the if else statement. When it comes to the frontend which should decide what strategy to use buttons are good way to delegate the decision further to the user. But buttons are the only solution I can think of right now and I know that often we cannot use them. So do we eventually end up using the if else statements? Does that also imply that generally enums are bad because enums often represent what strategy to use?

this is excellent

@geekific

2 жыл бұрын

Thanks a lot :)

Please does the PaymentService implement the Dependency Injection either?

@geekific

Жыл бұрын

With the help of @Setter from Lombok we made use of the setter injection. Feel free to check this video for more info: kzread.info/dash/bejne/eXWItbqmZ7qnqLg.html. Cheers!

@miratechsolutions5777

Жыл бұрын

@@geekific Thank you!

@miratechsolutions5777

Жыл бұрын

@@geekific Great explanation thanks again!

What is the difference between dependency injection and strategy pattern?

@geekific

Жыл бұрын

Hello, you can find our Dependency Injection video here: kzread.info/dash/bejne/eXWItbqmZ7qnqLg.html. Please take a look, and let me know if you are still confused!

Is Strategy Pattern also an explanation of the Dependency Inversion principle?

@geekific

Жыл бұрын

It could be, but these are two different things. You can have multiple strategies implementing the same interface, but if you still depend on the implementation then DI is not being applied! Take a look at this and let me know if you still have questions: kzread.info/dash/bejne/eqN1mMOTgLWbe5M.html! Cheers!

@whogashaga

Жыл бұрын

​@@geekific "if you still depend on the implementation" What does this mean? Doesn't every strategy class have its own implementation?

@geekific

Жыл бұрын

@@whogashaga Watch the video!

Best and simple example in the world

@geekific

Жыл бұрын

Thank you!

Life saver

@geekific

2 жыл бұрын

Glad it was helpful!