I really find your teaching style efficient and useful. You explain the problem first, then show the solution, then you show a real-world use case. Really appreciate it ❤ Please continue with this design patterns real-world examples ❤❤❤
21:00 Why do you want to do manual entries to map. Anyway, spring injects the beans right, if you have specific names to all components. I dont see you're making two incompatable services to make compatable using adapter anywhere here. This is more of a kinda stratergy and factory, where you're deciding implementation runtime(stratergy) and getting bean based on decision(factory)
Agree, this is not adapter, but more like strategy pattern. Adapter is to make the interface compatible, implies the payment service implementation of “make payment” changes the adapter should hide it from the client. The client should still be able to call this method, but the adapter makes appropriate calls to facilitate the payment of the target class.
That's what I have done right. Only the mistake I haven't cover incompatible stuff by creating different method with name That's why it's confusing buddy. I will remake this with more meaningful usecase
@@Javatechie Design patterns are tricky, some of them look similar, the definition and intention should guide us. In your example Basant, instead of having different payment services, a better way of showing this pattern would have been, if say “Paypal” had a “process payment” method with one implementation say taking amount in integer or so and later it changed to a different one say taking a float or BigDecimal value, the client will call the adapter and the adapter would make the call to paypal with appropriate arguments and that way the client is hidden from the changes. You are almost there with your example, but it does not show the following point. Correct me if I am missing something. The Adapter Design Pattern solves this problem by defining a separate adapter class that converts the incompatible interface of a class (called the “adaptee”) into another interface (called the “target”) that clients require. Still enjoyed your presentation and found it useful. Thank you for taking the time to share your knowledge.Appreciate it!
I apologise for confusion . I relaise after read many comments . I could make it better by focusing more on the incompatible usecase. Thanks for detailed information @Phoenix I will remake this with clear context
21:00.. we can have one more abstract method returning gateway type(string).. so instead of storying class name in map.. we can store gateway type directly
I recently did same changes - where I created interface had three implementation class and my spring container has three beans. i had else if statement to assign it processor then i call unified method. Thanks for the constructor which is holding all the processors.
No need write a custom logic to populate map in constructor @ 23:00. Spring will autowire all the beans based on interface @Autowired private Map paymentProcessorMap;
@@Javatechie yeah exactly this i what I told in my comment, instead of manually mapping beans if we have name to to the component like @component ("paypalAdapter") so on...then when you do Map and do constructor injection spring will automatically injects all the components that implemented PaymentProcessor
Hi, The concept is clear on the adapter. I tried it using qualifiers but changes required in qualifier annotations, Again and again I am required to change parameters Could you make one video on qualifiers where they do not require to change as in this video based on parameter gpay object created
I love your knowledge sharing but for this tutorial is not adapter pattern. It's strategy pattern combining to factory pattern. An adapter wraps one of the objects to hide the complexity of conversion happening behind the scenes. The wrapped object isn’t even aware of the adapter. For example, you can wrap an object that operates in meters and kilometers with an adapter that converts all of the data to imperial units such as feet and miles. Here you wrap anything
Hi Basant your video is nice but I think this is not adapter pattern this looks like Strategy pattern where we are selecting one strategy dynamically based on user input
@@CenturionDobrius i never delete anyone's comment buddy irrespective of good or bad . Because all the way i am learning so Let me check with my team and sorry for it . Please add it again . Thank you for appreciating my work
I really find your teaching style efficient and useful. You explain the problem first, then show the solution, then you show a real-world use case. Really appreciate it ❤
Please continue with this design patterns real-world examples ❤❤❤
Thank you buddy for appreciating it 😀. Keep learning
Thank you Basant sir. I really like your way of teaching.
21:00 Why do you want to do manual entries to map. Anyway, spring injects the beans right, if you have specific names to all components. I dont see you're making two incompatable services to make compatable using adapter anywhere here. This is more of a kinda stratergy and factory, where you're deciding implementation runtime(stratergy) and getting bean based on decision(factory)
Agree, this is not adapter, but more like strategy pattern.
Adapter is to make the interface compatible, implies the payment service implementation of “make payment” changes the adapter should hide it from the client. The client should still be able to call this method, but the adapter makes appropriate calls to facilitate the payment of the target class.
That's what I have done right. Only the mistake I haven't cover incompatible stuff by creating different method with name That's why it's confusing buddy. I will remake this with more meaningful usecase
@@Javatechie Design patterns are tricky, some of them look similar, the definition and intention should guide us.
In your example Basant, instead of having different payment services, a better way of showing this pattern would have been, if say “Paypal” had a “process payment” method with one implementation say taking amount in integer or so and later it changed to a different one say taking a float or BigDecimal value, the client will call the adapter and the adapter would make the call to paypal with appropriate arguments and that way the client is hidden from the changes.
You are almost there with your example, but it does not show the following point. Correct me if I am missing something.
The Adapter Design Pattern solves this problem by defining a separate adapter class that converts the incompatible interface of a class (called the “adaptee”) into another interface (called the “target”) that clients require.
Still enjoyed your presentation and found it useful. Thank you for taking the time to share your knowledge.Appreciate it!
I apologise for confusion . I relaise after read many comments . I could make it better by focusing more on the incompatible usecase. Thanks for detailed information @Phoenix I will remake this with clear context
Thanks you Basant for sharing this concept it will help many people interview point
Appreciate Basant your efforts!God bless you!👍🙏😊
Thank you, Basant, for uploading the video.
21:00.. we can have one more abstract method returning gateway type(string).. so instead of storying class name in map.. we can store gateway type directly
Yes that's a good suggestion 👍
I recently did same changes - where I created interface had three implementation class and my spring container has three beans. i had else if statement to assign it processor then i call unified method. Thanks for the constructor which is holding all the processors.
Thank you.
Awesome!!!!
Amazing ...
Hi Bro, interew questions, can you please share more details about transaction management
No need write a custom logic to populate map in constructor @ 23:00.
Spring will autowire all the beans based on interface
@Autowired
private Map paymentProcessorMap;
Ohh is it . Great let me try this. Thank you for the update buddy 😀
@@Javatechie yeah exactly this i what I told in my comment, instead of manually mapping beans if we have name to to the component like @component ("paypalAdapter") so on...then when you do Map and do constructor injection spring will automatically injects all the components that implemented PaymentProcessor
Thank you buddy. Interesting concept i was not aware about it.
Easy to understand this concept. Can you make video of Kafka connect to Snowflake database.
Kafka connect i tried but struggling to resolve the issue buddy need some more time to publish a content on it .
@@Javatechie thanks for the update!!
Hi,
The concept is clear on the adapter.
I tried it using qualifiers but changes required in qualifier annotations,
Again and again I am required to change parameters
Could you make one video on qualifiers where they do not require to change as in this video based on parameter gpay object created
@@parmodprajapati sure buddy will do that
Basant Bhai, We need "Port & Adaptor" design pattern, which is also known as Hexagonal Architecture Pattern..
Surely I will plan for it
@@Javatechieexactly please plan this. This helps alot in real time. Hexagonal, onion etc..
You beat me to it, was about to request Basant for the same. I have implemented it a year back but need a refresher and Basant explains it the best.
Yes.. Plan for this basant
Whats the difference between adapter and factory design pattern...i see both needs interface implementation.
Interface is the key bones of Oops buddy 😬
@@JavatechieI don't see much difference between adapter and factory
Entity Graphs ...can you make video with real-world examples
I love your knowledge sharing but for this tutorial is not adapter pattern. It's strategy pattern combining to factory pattern. An adapter wraps one of the objects to hide the complexity of conversion happening behind the scenes. The wrapped object isn’t even aware of the adapter. For example, you can wrap an object that operates in meters and kilometers with an adapter that converts all of the data to imperial units such as feet and miles.
Here you wrap anything
Hi Basant your video is nice but I think this is not adapter pattern this looks like Strategy pattern where we are selecting one strategy dynamically based on user input
My name is Basant not Hemant 🤣😂
@@Javatechiecorrected😂
this is not adapter pattern, it's more strategy/factory pattern...
Can I get some more insights on adapter design pattern buddy
💯
@@Javatechie really no need to delete my reply I was sincere with my answer.
And I really appreciate your work any way
@@CenturionDobrius i never delete anyone's comment buddy irrespective of good or bad . Because all the way i am learning so Let me check with my team and sorry for it . Please add it again . Thank you for appreciating my work
@@Javatechiethanks, and keep with high quality work !
Basant Bhai, we need videos on gRPC
Surely I will plan . Noted ✅️
Awesome! Been waiting for this as well. Everywhere it is Rest not grpc. It will be great if you take on grpc basant
Are you sure this is an adaptor pattern I think this is factory
Hello buddy could you please share some insights on adapter design pattern if it's not? I do mentioned it's combined of factory and DI injection
I also have same doubt
Not getting buddy how come it's factory design pattern ? Please watch the approach again and let me know
@@Javatechie this is not a factory for sure! But it has some sense of factory pattern.
Looks like factory design pattern