hi I think can we also use event type Observer Design pattern where NOtificationService will be out producer and EventListener will be out subsriber which is implemented by WhatsappMsgListener, EmailMsgListener, etc. and the events are images, json, xml, text,etc. Can you please guide whther I am thinking in the right way or not
Nice practical way of explaining design pattern. I have doubt on how to handle formatting of message/notification. For example - Product Delivery Email has to be formatted on different way than Slack/SMS.
amazingly explained, thanks a lot !!!
The explanation was really good. Please keep up the good work
Do like and subscribe and share with others 🙂
Nice explanation, understood everything clearly.
Glad it was helpful. Do like and subscribe and share with others 🙂
hi I think can we also use event type Observer Design pattern where NOtificationService will be out producer and EventListener will be out subsriber which is implemented by WhatsappMsgListener, EmailMsgListener, etc. and the events are images, json, xml, text,etc.
Can you please guide whther I am thinking in the right way or not
Nice practical way of explaining design pattern. I have doubt on how to handle formatting of message/notification. For example - Product Delivery Email has to be formatted on different way than Slack/SMS.
Man, you are awesome.
Isn t this the observer design pattern?
Thanks for the great explanation and example.
Amazing tutorial as usual . Keep up the Good work! (Y)
Kindly like and share 🙂
Can you please summarize which piece of code is only abstraction and which is only implementation exactly?