Factory Pattern in Java: Creating Objects with Ease 

Thank you!!

You are welcome!

Thank you for the awesome feedback.

Hey Daniel, thanks for your comment. Firstly, I agree with you that a switch or if statement in a separate class still looks like nested code at first glance. However, the alternative seems to be nested if-else statements with logic inside each condition, often in a single class. I've seen this too often in the 17 years that I have worked as a Software Engineer at multiple companies. The factory method pattern makes these statements: 1.) You still need a condition to determine which logic to invoke, 2.) But, the logic is decoupled into separate classes. The switch merely decides which implementation of an interface rather than having nested code in one place 3.) It is also centralized and not repeated every time your code needs to decide which payment option for example. In terms of the dependencies concern, check out our other video on how to make a factory method injectable: ru-vid.com/video/%D0%B2%D0%B8%D0%B4%D0%B5%D0%BE-WNzjz0v0t7o.html

You could use reflection yes. You could create an annotation called @FactoryMethod and then use reflection to auto-detect which classes implement a certain interface, or extends a certain abstract class :-) In this way, you could have abstract logic that generates a factory method in runtime, rather than having that switch visible in compile time. If you create such an annotation and it goes open-source, remember to reference campbelltech :-) We could collaborate on such a project.

I agree. It also violates the Single Responsibility Principle as one class (PaymentFactory) is being used for 3 responsibilities (Credit Card, Paypal, and Google Pay). Wouldn't it be better to make different Factories for different payment types (CreditCardPaymentFactory, PaypalPaymentFactory, GooglePaymentFactory)?

@@waynefaustorilla then that switch / nested if-else statement would be transferred to the client code. you have to make a decision, however.

You're welcome