Actually... This is the best video explaining observer pattern I've seen... From yesterday, I've been searching for observer pattern in both python and javascript, didn't find any video that solidified my understanding. I might have watched 5-10 videos (best ones).... I was sceptical at first since this video is in java (I don't know java) but turns out java is not as difficult as its often publicized. I actually understood everything clearly since I know python and JS Naveen's example of UA-cam was on point!!! If he had not taken youtube example, I think it would have been just another observer pattern video Java is also good!!! I'm liking the way it's written Now I'm gonna create this in JS
Thanks for explaining it in lucid way. Few things I noticed.. Subscriber class .. Channel channel = new Channel (); This is not required... You can remove the RHS part as you are doing in setter method.. Another improvement in UA-cam class is ... Unsubscribe is called only from subscriber side but not from channel side...
Sir, felt great, to be honest. I was struggling with this observer pattern and now it's all a matter of examples - you've made it that easy. And one more thing, with this online studying times, this study feels much more realistic with your appearance. Otherwise, only a study video makes it boring sometimes. Thanks a lot sir.
Hi Navin, Your videos and way of teaching are quite energetic. Even boring subjects you can explain with full of energy. Keep up the good work bro. Love and prayers from Pakistan !
I am impressed. Kudos. Explanation, engagement and I do not believe that you are getting enough props for ur work. If you have been my high school or college teacher ... :( , but thank you and will keep supporting sir :) :D :}
Your explanation is not academic. It's easy to understand! Thank you I'm just seeing your register numbers are 999K. Wow, congratulations! Hope you reach 1M subcribers point!!
Hello Navin, I have been watching your videos for a while now and I find them very useful. I really wish you could do a live stream some time so that we could interact with you.
Actually the observer pattern is much more abstract and braod than that. It has to be general. I know that you are trying to make it simple so everyone understands it, but in doing so, you missed the principle of the observer pattern which is to make code flexible and easy to be added to by creating interfaces and classes that implement the interfaces and then under these implementing classes we can have as many subscribers and channels as we want. The way you did it is just normal java code with no design pattern.
good explanation. so clear now. small doubt: during unsubscribing, only subscriber is removed from the list of subs in the channel object but not the channel field from the subscriber object. forgot ?
One doubt - Why are we calling subscribe on Channel and subscribeChannel on Subscriber? Say when a user clicks on subscribe, cant we just call subscribeChannel method, which also takes care of subscribe to that Channel? Since both have to be called inevitably on event, should they not be coupled? Please let me know.
Thanks for the interesting video. Just wondering, about the subscription method implementation part. Is it correct to keep two diff methods and call them separately? For example, when a subscriber subscribes to some channel, aggregation into the channel's list could be called in that method. Now, you can miss the subsequent subscribeChannel method call for the subscriber, and it will break the logic. I guess, it can be treated as a bug. Isn't it? Thanks
Hi, I have been working with TCP Socket, I want to know how can we observe data from socket and pass it to view (web page/jsp) in (Java Spring boot). Like a Real time data, to show Stock Market stats, with using any timer. Can you please help me with this issue. Thanks
Hey Naveen, I often get confused on how come Subscriber (Observer) get the update() method. And that method contains the "video uploaded" message. I think managing that message should be responsibility of channel (Subject)
Is this solution not susceptible to concurrent modification exception if there are additions and removal all at once in subscriber list assuming the subscribe and unsubscribe events would happen independently in separate threads in real world
Can you please make more python videos, some suggestions can be algorithms and ai, games using pygame, ethical hacking, data analysis and data visualization.
Hi Naveen, you are doing superb job. I just have a doubt in this Observer DP. We are calling telusko.subscribe(s1)... methods inside UA-cam class. but if we are already calling s1.subscribeChannel(telusko) then it shouldn't be necessary right?
Hey Telusko, thank you very much for your great videos! I got a simple question, are these patterns static in it's architecture or is it allowed, to change it for special use-cases? I rewrote this pattern by myself just to internalize the idea behind it, but called the method unregisterSubscriber and registerSubscriber from the class channel in the method unSubscribe and subscribe from Subscriber every time a subscription or unsubsctiption from a Subscriber takes place, so that the channel doesn't have to call the method explicitly and only gets informed about the new subscription or unsubscriptions. Also, evey time a new video is being uploaded, I don't call the update-method from subscribers, but send an update method from the channel class to all subscribers. Would that still count as observerpattern or is it strictly required that both sides have to register each other and the update method is in the class of those, who get informed? Keep up the good work, love it!
Subscriber class should not create "new" Channel Object every time (Subscriber.java : line 6), but rather a single channel should be created in UA-cam.java, and passed as dependency every time new subscriber object is created(either in constructor or as setter ), so that there is only one Channel object and multiple subscribers. Subscribers can then subscribe to the injected "Channel" object and get notified of any new videos uploaded by the channel.
I started following your tutorials in 2017. Now i am a full stack java developer...Thank you a lot
I can say one thing " ur examples are so Realistic easy 2 understand" keep it up Good work bro n Thank you :)
You are making life easier for java developers
Love from Pakistan :)
I discovered this channel a few months ago and I'm legit loving it!
Actually... This is the best video explaining observer pattern I've seen...
From yesterday, I've been searching for observer pattern in both python and javascript, didn't find any video that solidified my understanding. I might have watched 5-10 videos (best ones).... I was sceptical at first since this video is in java (I don't know java) but turns out java is not as difficult as its often publicized. I actually understood everything clearly since I know python and JS
Naveen's example of UA-cam was on point!!! If he had not taken youtube example, I think it would have been just another observer pattern video
Java is also good!!! I'm liking the way it's written
Now I'm gonna create this in JS
Thanks!
I have watched multiple observer design pattern video, I must say this is the best one and more realistic. Keep it going boss..
Thanks for explaining it in lucid way. Few things I noticed..
Subscriber class ..
Channel channel = new Channel ();
This is not required... You can remove the RHS part as you are doing in setter method..
Another improvement in UA-cam class is ...
Unsubscribe is called only from subscriber side but not from channel side...
Your thinking way is very appreciatable.Thanks to show me this way of logic building.
Wonderful explanation and the example of the Observer Pattern I have ever seen! You are my favourite Teacher. Thanks.
Its really amazing that....this lengthy process is very easy to understand by you Sir😍😍😍😍
Easily able to understanding by giving simple examples with clear explainations. Thanks Naveen.
All the playlists were really very good and informative. Thanks, Navin for such wonderful content.
You are GOAT teacher, your explanations are also GOAT
Thank you for such a great content, keep going!
Quick and nice explanations that's very easy to understand - telusko learnings. From this channel ,I have learnt a lot. Thanks much Navin
Sir, felt great, to be honest. I was struggling with this observer pattern and now it's all a matter of examples - you've made it that easy. And one more thing, with this online studying times, this study feels much more realistic with your appearance. Otherwise, only a study video makes it boring sometimes. Thanks a lot sir.
Hi Navin,
Your videos and way of teaching are quite energetic. Even boring subjects you can explain with full of energy. Keep up the good work bro.
Love and prayers from Pakistan !
I am impressed. Kudos. Explanation, engagement and I do not believe that you are getting enough props for ur work. If you have been my high school or college teacher ... :( , but thank you and will keep supporting sir :) :D :}
Please continue the series. It would be very much helpful.
finaly, with your exemple i understand how to implement the observer pattern. you are the best.
Par excellence ! Perfect explained. Perfect example. Especially direct programming in the java. Keep on !
Hi naveen, can you also make videos on Java memory management and how to improve performance of java applications.
This is called teaching!
Excellent
Every time...learn new from telusko, and waiting for micro services series
can not agree more，there is nealry no very good lesson for micro services. Waiting for it too. I have watched so many lessons of telusko
@@qingsiji1638 check java brains(Kaushik) for microservices
Thanks Telusko. Your examples are very intuitive and helpful. I am able to learn Observable Design Pattern easily now
Your explanation is not academic. It's easy to understand! Thank you
I'm just seeing your register numbers are 999K. Wow, congratulations! Hope you reach 1M subcribers point!!
well explained🔥Also try to upload the other design patterns as well it will be very useful for us...!!
Hello Navin, I have been watching your videos for a while now and I find them very useful. I really wish you could do a live stream some time so that we could interact with you.
Hi Navin, I really have to say this. thank you. you surely are changing my life for good. keep up the good work.
I purchased a GFG course about System Design but that is not at all good but this video cleared my doubts.
Thanks a lot 🙏 Expecting more videos like this.
Thanks Naveen . You have explained it very well.
Well explained. Just one potential correction - upload() is storing video title to channel title.
Still helpful after 4 years❤
It's very realistic example. This is more than enough to understand the pattern. Good Convey....
Actually the observer pattern is much more abstract and braod than that. It has to be general. I know that you are trying to make it simple so everyone understands it, but in doing so, you missed the principle of the observer pattern which is to make code flexible and easy to be added to by creating interfaces and classes that implement the interfaces and then under these implementing classes we can have as many subscribers and channels as we want. The way you did it is just normal java code with no design pattern.
Absolutely true
yes brother I thought the same thing
I was going to comment it. Thanks for noticing
U rocks always...
Student of telusko...
Thank you sir. I was looking for visitor pattern video and found this new concept. Thanks a lot
Wow simply explained observer design pattern easily .. thank so
Simply super😍🤟Thanks..
such an easy to understand example! thank you :)
Amazing series....can we have more design patterns explained through some more videos under this playlist?
Your example was awesome! Thanks, bro :D
thank you very much very simple and easy to understand
Please continue this series...
I got very good understanding with ur explanation sir.Thank you!!
Thank you Naveen for your awesome videos.
Just mind blowing sir!
Yeah I always waiting for your video content .... Everytime
Crystal clear, thanks a lot!
Brilliant analogy !!!
good explanation. so clear now.
small doubt: during unsubscribing, only subscriber is removed from the list of subs in the channel object but not the channel field from the subscriber object. forgot ?
thank you so much sir. very clear explanation.
how to notify the subject that an observer has unsubscribed???
I subscribed to be an Observer of this channel.
One doubt - Why are we calling subscribe on Channel and subscribeChannel on Subscriber?
Say when a user clicks on subscribe, cant we just call subscribeChannel method, which also takes care of subscribe to that Channel?
Since both have to be called inevitably on event, should they not be coupled?
Please let me know.
Just amazing, a smart way to explain things, Thank u soo much
you have great explanation skills :D
In 11:42 kindly elaborate why perform s1.subscribeToChannel(telusko);
I tried without it then video title got null . Thank you .
Hi Naveen, Kindly make video recordings for all 23 design patterns, hope we have few recordings already and kindly help us with the missed ones.
Superb explanation Thank you Sir...
Good Explanation..Thank you
Great video code along, this really helped me put the theory into practice. Thank you
Superb explanation
thank you for this awesome explanation!!!!
It was awesome to follow all of design pattern videos. Could you cover all the other design patterns as you said we have to know all?
Very understandable way , thankyou telusko
Great Explanation. Good Example.
Thanks for the interesting video. Just wondering, about the subscription method implementation part. Is it correct to keep two diff methods and call them separately? For example, when a subscriber subscribes to some channel, aggregation into the channel's list could be called in that method. Now, you can miss the subsequent subscribeChannel method call for the subscriber, and it will break the logic. I guess, it can be treated as a bug. Isn't it? Thanks
Sir, u r genius !
Hi, I have been working with TCP Socket, I want to know how can we observe data from socket and pass it to view (web page/jsp) in (Java Spring boot). Like a Real time data, to show Stock Market stats, with using any timer. Can you please help me with this issue. Thanks
1:57 pulling
2:32 observer = subscriber
3:50 1 subs : 1 channel
Amazing explanation !
It should print who is uploading as well and we can use getter for title. The example would be better if there was case without and with observer.
U just earned a subscriber.
Awesome sir... 🙂
Great work sir...pls make a design pattern series
Thanks, example is matching to observer pattern
Awesome I can use this concept with JavaScript too. Thanks a lot
Hey Naveen, I often get confused on how come Subscriber (Observer) get the update() method. And that method contains the "video uploaded" message. I think managing that message should be responsibility of channel (Subject)
Is this solution not susceptible to concurrent modification exception if there are additions and removal all at once in subscriber list assuming the subscribe and unsubscribe events would happen independently in separate threads in real world
Since you are making videos of Design Patterns, can you provide explanations of the various patterns using functional style?
Can you please make more python videos, some suggestions can be algorithms and ai, games using pygame, ethical hacking, data analysis and data visualization.
Hi Navin, Can you please upload more design pattern video, If possible can you please give any existing example which Java is used internally.
Great content! Thank you so much 👍🏻
Hi Naveen, you are doing superb job. I just have a doubt in this Observer DP. We are calling telusko.subscribe(s1)... methods inside UA-cam class. but if we are already calling s1.subscribeChannel(telusko) then it shouldn't be necessary right?
Hey Telusko, thank you very much for your great videos!
I got a simple question, are these patterns static in it's architecture or is it allowed, to change it for special use-cases? I rewrote this pattern by myself just to internalize the idea behind it, but called the method unregisterSubscriber and registerSubscriber from the class channel in the method unSubscribe and subscribe from Subscriber every time a subscription or unsubsctiption from a Subscriber takes place, so that the channel doesn't have to call the method explicitly and only gets informed about the new subscription or unsubscriptions. Also, evey time a new video is being uploaded, I don't call the update-method from subscribers, but send an update method from the channel class to all subscribers. Would that still count as observerpattern or is it strictly required that both sides have to register each other and the update method is in the class of those, who get informed?
Keep up the good work, love it!
Thank you so much Telusko
Amazing explanation
Subscriber class should not create "new" Channel Object every time (Subscriber.java : line 6), but rather a single channel should be created in UA-cam.java, and passed as dependency every time new subscriber object is created(either in constructor or as setter ), so that there is only one Channel object and multiple subscribers. Subscribers can then subscribe to the injected "Channel" object and get notified of any new videos uploaded by the channel.
@Telusko @Navin which software do you use to create video. Presentation and you video in it
For me calling the upload method in main shows null at the output
Hi Naveen, Can you make a video on difference between Observer dp, state dp and pub-subs dp
Actually very nice example.....
Great explanation thank you so much.
telesco.subscribe(sn) seems incorrect as channels do not subscribe. Instead s1.subscribeChannel(teleaco) should have called it internally.
V good clear video
you could've put the subscribeChannel method inside the subscribe method. Still a great vid
hello sir, aint u suppose to use interfaces instead? because we got so many methods which end up confusing..
W'll inform everyone..hahaha...best explanation ever