Only because of your spring boot master class I made transition as a Java backed developer from QA with 70% hike. Whoever is gonna follow your videos along with hands on no doubt, sure they'll rock. Thank you so much for all your efforts and guidance.
Great video. One question - For Abstract Factory pattern - you have taken Application application = new Application(new MacUIFactory()); But if we use some string like new Application("mac"); and write the logic inside application. That way the work is simple for end user as he doesn't need to write java syntax like 'new and constructors()'. But again this has another disadvantage - we need to hardcode the application class like - if "mac" { return new MacUIFactory(); } and that violates 'Open/Closed principle'. so a hybrid solution is to use a list and dynamically add / fetch the UI factories based on the string passed like "mac". This way we follow principles like Dependency Inversion, open closed, in general all the Solid principles.
Thanks Shabbir for all these videos. You really explain well. I understood microservices because of your microservice course on Udemy. I had tried many other courses as well but your course was the best. Thank you for your courses and videos, I have learnt a lot and grown as a java developer and I slightly envy your vast knowledge🙂. I hope I reach that level where I have the clarity to explain to others.
It's really very easy to understand things with an example. And you have done it very well in this video. Understanding design patterns by just reading the definition is hard but with an example it gets easy to understand. Thanks for the video, it's very helpful
You nailed the Singleton pattern. Thanks !. But, most of the time instead of enums we need to use notmal Objects. So we can stop reflection using throwing a Runtime exception in the constructor if the Object is not null. So then no one can't create an instance direct calling the constructor if the object already created.
Hi shabbir, thankyou so much, i really like learning from you channel.. btw can i request a tutorial spring cloud microservice with kubernetes (kustomize) ?
Your factory Design pattern example violates the open closed principle. This is a bad code example, if someone asks you in an interview the solid Desin pattern and then just after that the factory design pattern then with the example shown here, then you are doomed.
Just realised it also breaks the Dependency inversion principle. The higher level class (OperatingSystem) shouldn't depend on the lower level class (WindowOperatingSystem, LinuxOperatingSystem) , but it should depend on the abstraction
But its a fundamental concept to build upon before going into design patterns, therefore it makes perfect sense to cover in this video. Great work Shabbir!!!
Jan 1, 2025 06:24PM | Watched upto 20:20
Jan 1, 2025 09:11PM | Watched upto 39:39
Jan 1, 2025 09:25PM | Watched upto 48:35
Jan 1, 2025 10:22PM | Watched upto 56:30
----------------------------------------------------------------------
Jan 5, 2025 03:27PM | Started 56:31
Jan 5, 2025 04:04PM | Watched upto 1:12:34
Jan 5, 2025 04:33PM | Watched upto 1:24:51
----------------------------------------------------------------------
Jan 12, 2025 5:07PM | Started 1:24:52
Jan 12, 2025 6:19PM | Watched upto 1:34:55
Jan 12, 2025 7:23PM | Watched upto 1:43:02
Jan 12, 2025 8:32PM | Watched upto 1:52:15
----------------------------------------------------------------------
Jan 13, 2025 7:30PM | Started 1:52:15
Only because of your spring boot master class I made transition as a Java backed developer from QA with 70% hike. Whoever is gonna follow your videos along with hands on no doubt, sure they'll rock. Thank you so much for all your efforts and guidance.
Can you tell me how did you make transition as every where these days people ask experience in developer role
That is awesome!
Thanks! Shabbir ,small token of appreciation
Thank you so much 🙏🙏
Great video. One question -
For Abstract Factory pattern - you have taken
Application application = new Application(new MacUIFactory());
But if we use some string like new Application("mac"); and write the logic inside application. That way the work is simple for end user as he doesn't need to write java syntax like 'new and constructors()'.
But again this has another disadvantage - we need to hardcode the application class like - if "mac" { return new MacUIFactory(); } and that violates 'Open/Closed principle'.
so a hybrid solution is to use a list and dynamically add / fetch the UI factories based on the string passed like "mac". This way we follow principles like Dependency Inversion, open closed, in general all the Solid principles.
Thanks Shabbir for all these videos. You really explain well. I understood microservices because of your microservice course on Udemy. I had tried many other courses as well but your course was the best. Thank you for your courses and videos, I have learnt a lot and grown as a java developer and I slightly envy your vast knowledge🙂. I hope I reach that level where I have the clarity to explain to others.
Could see how much effort you have put on these videos. Made it so simple to understand. Great work and thanks.
I appreciate that!
It's really very easy to understand things with an example. And you have done it very well in this video. Understanding design patterns by just reading the definition is hard but with an example it gets easy to understand. Thanks for the video, it's very helpful
Glad it was helpful!
Thanx bro for putting to much effort for creating this worth it content.
Great effort from you. Keep rocking. All the very best. Thanks for all your videos.
Thanks 🙏🏻
You nailed the Singleton pattern. Thanks !. But, most of the time instead of enums we need to use notmal Objects. So we can stop reflection using throwing a Runtime exception in the constructor if the Object is not null. So then no one can't create an instance direct calling the constructor if the object already created.
good lectures wish you contribute your effort for humanity and not influenced by any EXTREMISTS
Thank you shabir. It was worth watching. God Bless you 🌸
It's a great video and it will very helpful for both students and Experienced professions
Thanks 🙏🏻
34:06 the class needs to implement Serializable. Great video thank you.
Singleton can be broken by calling clone(). Either we need to throw exception or the instance.
Great effort. Awesome content.
Glad you liked it!
Really great examples!
Thank you man this is awesome.
The video is good but in the builder design pattern shouldn't you initialize Burger class attributes set in Burger Builder
I felt flyweight design pattern to be similar to prototype design pattern. Is there a way for distinction or use case to prefer one over another.
Thanks Shabir. Good examples
Excellent explanation, many thanks :)
Excellent explanation budyy
Love it!!!!!!!!!!! Thanks fro Sharing!!!!!!!!!!!!!!!!
Thanks 🙏🏻
A big love💌
🙏🙏
can you please share your git repo link, so that it will be handy...........thanks for all the work
We can't break Singleton pattern by Serialization if we don't implement Serializable interface, Isn't it?
Gold Mine!!
Hi shabbir, thankyou so much, i really like learning from you channel.. btw can i request a tutorial spring cloud microservice with kubernetes (kustomize) ?
Great Work bro
Thank you so much 😀
fantastic ever!
Thank you! Cheers!
Thank You
You're welcome 🙏🙏
where can we find SOLID desing principles are not design patterns
Super 👍
Thanks 🙏
Great video
What is the code editor that you use ?
Thank you ..bro
THank you so much !
Welcome!
Can we get all solid principles masterclass
You seem to have lot of patience to create video like this
That’s his passion
greatt bhaii
This is gold
🙏🏻
1:48:00
Thanks
Welcome
Visitor pattern missed
please create video from spring batch . not use default database spring batch. use custom database
Thank you so much!!
You're welcome!
Pls cover some lld questions
Factory pattern violates the open closed principle...., thats why abstract design pattern...
O bhai solid design principle hota h na ki pattern
O bhai acha hua bata diya 🤣
Continue from 30:49 August 08, 2024
Your factory Design pattern example violates the open closed principle. This is a bad code example, if someone asks you in an interview the solid Desin pattern and then just after that the factory design pattern then with the example shown here, then you are doomed.
Just realised it also breaks the Dependency inversion principle.
The higher level class (OperatingSystem) shouldn't depend on the lower level class (WindowOperatingSystem, LinuxOperatingSystem) , but it should depend on the abstraction
bro SOLID Principles is not design pattern
But its a fundamental concept to build upon before going into design patterns, therefore it makes perfect sense to cover in this video. Great work Shabbir!!!
@@syednoman84 I agree
When are you gonna create a threads 🧵 account? 🤔
Shoul I ?
@@DailyCodeBuffer Yea. Why not? Be ahead of everybody else.
thanks
You're welcome!