Low Level Design 105 | Single Responsibility Principle in SOLID | 2022 | System Design
ฝัง
- เผยแพร่เมื่อ 13 ต.ค. 2024
- Learning system design is not a one time task. It requires regular effort and consistent curiosity to build large scale systems. Moreover, every system has different requirements and meeting them requires expertise and people with varied and specific knowledge. There are a lot of resources to learn through videos. But not everyone enjoys that mode of learning. Instead some people understand things better by reading and thinking on the points put forward by the author. Such people can access these in different ways - blogs, articles and books. We have come up with this video to put light on one such aspect, that is - Single Responsibility Principle
Important links and resources:
✒ github.com/top...
✒ Quick summary: docs.google.co...
------------------------------------------------------------------
Recommendations
------------------------------------------------------------------
Our full courses on youtube:
✒ System Design Primer Course: • System Design Primer C...
✒ REST APIs made easy: • REST APIs MADE EASY
Some paid courses that we recommend:
✒Educative.io: bit.ly/3qnW5ku
✒Interviewready.io: get.interviewr... (Use coupon code SUDOCODE for extra discount)
------------------------------------------------------------------
About Us
------------------------------------------------------------------
Created and Instructed by:
Yogita Sharma
✒ LinkedIn - / yogita-sharma-83400b55
✒ Instagram - / sudo.code1
✒ Facebook - / sudo.code
✒ Medium - / yogita088
Post-production(editing, thumbnail etc) managed by:
CiKi
✒ Website: www.ciki.co.in
✒ LinkedIn: / 74735937
Colors and design by:
Naini Todi
✒ LinkedIn - / nainitodi
Both Arpit and Yogita are software engineers and want to help other software engineers become better by providing high quality and well researched content by adding their creativity and teaching twist.
------------------------------------------------------------------
Join Us
------------------------------------------------------------------
Hangout with sudoCode:
✒Discord Server: / discord
For business:
✒Email: sudocode.yogita@gmail.com
Yogita, you're just amazing! Thank you for bringing such content to us. The way you explain so much in a limited amount of time is commendable.
I understood SRP clearly for the first time. What an amazing explanation! Your examples are really good too, thanks for giving two examples with slightly different perspectives
Loving this LLD series. Patiently waiting for the Open/closed principle! 🙏🏽
Hi Yogita
Thanks for the amazing explanation
I have a doubt:
1) Instead of making different classes for each responsibility, why can't we make different private methods in the same class for different actors. Like getRegularHoursForCFO(), getRegularHoursForHR(). This will solve the problem in the example you mentioned.
In case of contructors, we can do overloading.
You are the smartest person I have ever seen explaining Low-Level Design. Thank you very very very much 😍😍♥♥♥♥
I am addicted to your way of teaching.It gives me more and simple ways of learning topics.Thank you.
Thanks, Yogita excellent explanation, but I can't see the video for the Open-closed principle in the playlist.
Hi Yogita,
First, You are doing great job and I am learning something new in the end after watching every video of yours. Keep up the work!
Second, I have doubt in the both the examples. Even though we decomposed the methods to different classes, still impact is there when change happens. For example, getCalculateHours is still needed for both CFO and HR. where this method will sit? and when change is required, still both classes have impact, right?
In another example , if Bill Store class required new param like isPaid, anyway that should be sent by Bill class as that new param is relevant to Bill object. Again, change is needed on Bill class.
Please correct if my understanding is wrong.
Same question im having if you got the answer plz comment.
method getCalculateHours would reside on both classes, would be private to those particular class, hence any change done for getCalculateHours of calculateHours wont affect implementations in calculateSalary.
The best graphics, I've seen in any video so far! Literally graphics are one of the USP of this series.
Thanks for putting such great quality content!
Good job! So many people get this wrong, especially other content creators.
Thank you for helping debunk the dogma around S.R.P. 🎉
The best explanation on this topic on youtube
Thanks a lot ma'am for explaining in easiest way
Yogita thank you so much for bringing such a great content. I’m an aspiring technical architect this will surely help me.
This is an AMAZING explanation. I have been looking for a really good explanation of the single responsibility principal for years to truly understand it, and this takes the cake!
You are a gem. Thanks for explaining it in the best possible way while breaking the myth. Appreciate your efforts. It helps a lot in preparing the LLD preparation.
Hi yogita, can you pls upload videos more frequently so that i can stick to your playlist.. ideally if you can upload 3+ videos per week it would be really great for prepping for interview.
Yogita, your videos are well researched, well narrated and well presented!
I feel so much comfortable watching videos, because I can trust whatever you're saying.
The explanation was crystal clear, especially for the Hotel example.
if isPaid is added with the getter and setter method instead of constructer, how would that break?
Honest efforts in making these videos. Very helpful !!
Glad you like them!
Yogita. you are amazing on the explanation. Do we have 2nd design principle Open Close?
Can you give an example where srp is followed and the class has more than one method.
Thanks.
Loved the video :)
well this was quite clearly explained , really thanks for this
Such a great explanation of this concept. Thank you!
But if both calculateSalary and calculateHours methods use the same getRegularHours (maybe it will be a little different for each type), but if you separate it, will the code be duplicated? And although the editing is independent, if additional operations are needed, do we have to edit it in 2 places instead of editing it in 1 place?
Great video and breakdown of SRP. I don't know who out there thinks one public method on a class is a good practice, but they definitely have their wires crossed.
Then in this case one class can have mostly one pulblic method when it comes to real time implementation.
Can't argue with your explaination, very clear....
Thanks yogita for amazing content, would it also be possible for you to make a video on open closed principle. Rest all the solid principles are covered really well in great detail
Couple of correction for the viewers of this video from my point of view,
- Clean code book has no dedicated topic or chapter for SOLID.
- Uncle Bob[Robert Martin]'s other two books Agile Software development PPP and Clear architecture are talking on this topic in detail.
- SRP can be viewed from different level like Functions and Classes, Component and architecture. At each level same principle is sharing some insight. This video is presenting one view of it however, it doesn't mean that There should be a single reason to change a class is incorrect and that's not what SRP is. People who are confused can Read SRP principle from both the books that I mentioned above.
By heart I am appreciating author's good quality work and commitment to sharing with community however, above points are extension and slight correct to guide users on further reading.
In fact, in the Agile Software Development PPP book, at the beginning of the SRP chapter, it explicitly states "A class should have only one reason for change."
Hi @sudocode, Thanks for the explanation, but one doubt here by seeing the explanation - how a developer will know beforehand that who the different stakeholders can modify the code?? For ex in a class having different methods, how will a developer know while designing that needs to segregate the methods to different classes based on stakeholders beforehand?
Does applying object oriented design to real world models come with experience?, thanks a lot for replying.
I would highly appreciate your reply
Not completely through that. It's more like you should have an understanding of oops concepts well. And then of course, the more you practice, the better you would get at it.
@@sudocode thanks a lot! I love watching your content!
awesome explanation.. there is no other video which explains this principle so clearly...
Does the additional method of subclass violate the LSP which is not present in the parent class?
A small doubt, if we separate also, still CalHours need to used by CalSalary need to know regularHours(), so where do we need to place this ? If it write in two classes are we not violating DRY ? Please comment
Hey excellent teaching love you please don't stop uploading
amazing graphics, very nicely explained and a very well delivered video, thanks for your hardwork, I got to learn something useful today
Ma'am, please, also explain the other parts of SOLID principle.
Really, awesome 😊
Thank you for the quality content.Please make more videos in the LLD series.
Finally I found a best vdo in TH-cam ❤️
Thats the idea behind common closure principle (CCP) & Applying DDD (Domian Driven Design) - The basic idea behind microservices
Yes!
very very helpful for me for learning LLD
Seriously , great explanation
Thanks Yogita. I can learn very well.
Great Content. thanks yogita
amazing. waiting for next vids in course
amazing logical explanation
Hey,
Could you please explain how in the first example decomposition to different class would help us if for CFO we need to make changes in common getWorkingHours method?
Also in 2nd example if we need to add more fields in db, even if we create new store class, we would still need to pass isPaid from bill class to store it.
Eagerly waiting for your response for clarification on these.
Thank you
Thanks Yogita for sharing such useful content !! You are an inspiration...
I sometimes get confused while breaking the classes and end with lot many classes like models(with mainly properties and getters setters), service classes (service class for model classes to perform certain tasks like play, save, move, etc) and repositories (for saving objects in memory).
Could you help me understand if this approach is correct or not?
Is it fine to have separate service classes for having the business logic instead of putting a lot in model classes.
If yes, should I create it as a singleton class, class with static methods or like a normal class, because it will be mostly performing business logic without maintaining any state.
It is okay to break classes into multiple model classes. If there are N entities (credit card, user, cart,classes etc..) you can create different model for each of these like (credit card model, user model...ETC). You can use get;set methods to wisely encapsulate the porperties of the model class also. If you look at MVC architecture. This is how it is done. Model classes hold data and service classes are used to apply bussiness logic on top of these models.
Making all the methods static and using singleton is not a good idea. As you practice solving LLD problems and multiple design patterns you will understand the beauty of OOP. If your not using OOPS to max ability then your just using Functional programming with model classes.
Top notch explanation, thank you very much!
Hi . It's very helpful courses for OOP ,OOD and more, thanks for your efforts
👍🙂
@@sudocodeMam please complete remaining video of solid principles. Your explanation is amazing 👍
thanks for nice tutorial ,
but what happen for the "getRegularHours()" method in first example after separation classes? how can fix share code in two class ? duplicate code or using interfaces?
Great explanation. Thank you
Amazing Superb explanation. thanks from my heart :)
Happy teacher's day guru ...🙏
Thank you so much for the wish. At least I got one wish on teachers day. I will keep it. Thanks again.
crystal clear explanation
Superb explanation !!!
Oh, I was looking for something else, and saw your thumbnail!
You look so like *NAIROBI* from _La Casa de Papel_ :)
Hahaha thanks. I get that a lot.
Could you make video for second principle of solid ie. o - open/closed principle?
Amazing explaination! Learning a lot here
Thanks for this, it really helps me as a student hehe can't wait to watch the Open/closed principle :)
Super content! Please increase the upload frequency Yogita! :(
Videos in this series are very good . If it is possible could you please upload more content
Awesome... Lucid ...
Good explanation ❤....
Awesome explanation.
Informative video and nice animation...keep posting 😊
Thanks Anek
Very good explanation 🤩
Great 👍
Great explaination! Thanks for such amazing content!
Mam, where is the open close principle? You lecture 106 is not open close principle.I dont want to move to L without knowing O. If anybody has the title,please let me know
Can't wait to see your next video
Waiting for more videos didi 😄
Where's Open Closed principle? It's not existing in your list
appreciate your work.
So, can we make it a thumb rule that - If there are more than one actors for a method then just make it a class?
Thanks for this video
Congratulations mam u got a new subscriber
it's me 😁
Thanks for the great content!
Now when i give this ans to interviewer. Hoping he would have read uncle Bob too or have seen your explanation😊
mam thanks really
I am bca first semester student,after I will also do MCA than Can I eligible for FANG company.
This is true layman terms from coding perspective that everyone seeks. Thanks for not following the traditional bookish knowledge.
Brilliant !
Amazing 😍
Thank you! Cheers!
When are you uploading open close principle?
It will take some time.
Why more video are not comming now days and this particular series of lld
Will come soon.
Thank u
When you will cover design patterns?
After solid principles
@@sudocode will be waiting for that,
Thank you❤
Thanks backlogbatch 😇
Understood
Hey mam wonderful explanation mam thank you so much mam 🤗🤗🤗................................................
:-)
I thought I'd seen the most beautiful programmer but I was wrong.
ma'am please make more videos
Wow.
Please share the contents in slow way. Most of the things will go to out of our mind
I am really sorry for the speed. Please bear with few more videos as those are record. Will make sure doesn’t happen in new ones.
Yes, that is one of the problems with the videos like too much content in a single sentence. Despite this, the content is good and the teaching is also good.
I'm literally falling in love with you
I m in love with u maam😍
Hi Yogita,
I am loving the content you are posting on TH-cam. In one of your Low level design videos (th-cam.com/video/FbQYifw9Be8/w-d-xo.html) , you mentioned Obect oriented design is hard, what do you mean by that, does it mean it is really hard to grasp low level design, could you clarify that. Your response will be highly appreciated!
I appreciate your persuasion skills but you have exhausted every possible way of communication to get answer for this question. Yes it is hard to convert real world models to object oriented design due to its subjectivity and the requirements in place. It’s not hard to grasp, it’s hard to apply.
Please try to be patient while asking questions. Attention seeking never helped anyone progress.
@@sudocode thanks a lot and I understand, I wont bug a lot in future
@@sudocode just one last question,Does applying object oriented design to real world models come with experience?, thanks a lot for replying.
You are not actually teaching for interviews it seems - I mean, that could be a side effect, but not the target.
what I have seen in TH-cam is things been spit out and asked to be remembered. This is far from it.
Aap ko hindi nahi aati
Aati hai. Aur aapko english?
@@sudocode yes mujhe english nahi aati aap hindi english mix kro please