filmov
tv
Solid Design Principle Interview Questions and Answers for fresher and experienced | Code Decode
Показать описание
In this video of Code Decode we have covered Solid Design Principle Interview Questions and Answers for freshers and Experienced
Udemy Course of Code Decode on Microservice k8s AWS CICD link:
Course Description Video :
SOLID Principles Covered with live demo. With steps on how to implement these in day to day life.
Why we need solid Principle?
The broad goal of the SOLID principles is to reduce dependencies so that engineers change one area of software without impacting others. Additionally, they’re intended to make designs easier to understand, maintain, and extend. Ultimately, using these design principles makes it easier for software engineers to avoid issues and to build adaptive, effective, and agile software.
they lead to better code for readability, maintainability, design patterns, and testability.
What are solid Principles?
The following five concepts make up our SOLID principles
Single Responsibility
Open/Closed
Liskov Substitution
Interface Segregation
Dependency Inversion
What is Single Responsibility Principle in solid principles?
It states that “One class should have one and only one responsibility”
Which specifically means - we should write, change, and maintain a class only for one purpose.
Change Class only when you need to change state of one particular object or instance
Example : POJOS follow SRP.
Suppose we have Employee and Address Class, If we want to change the state of Employee then we do not need to modify the class Account and vice-versa.
If you world have merged both as single POJO , then modification in one field for address (like state ) needs to modify and Whole POJO including Employee
Worst Design - which don’t follow SRP Hitting Database in POJO of Employee Class. That’s why we have service layer, DAP layer and Entities separated.
Why is Single Responsibility Principle IMP?
In Real world, Requirement changes and so does your code implementation to cater the changing requirement ,
The more responsibilities your class has, the more often you need to change it. To prevent frequent changes to same class,
Testing is easier - With a single responsibility, the class will have fewer test cases
Easier to Understand
Less functionality also means fewer dependencies to other classes.
So best practise says : Use layers in your application and break God classes into smaller classes or modules
What is Open/Closed Principle in solid principles?
It states that “Software components should be open for extension, but closed for modification”
The term “Open for extension” means that we can extend and include extra functionalities in our code without altering or affecting our existing implementation.
The term “Closed for modification” means that after we add the extra functionality, we should not modify the existing implementation.
In real world, You must have noticed that you change something to cater a new requirement and some other functionality breaks because of your change. To prevent that we have this principle in hand. It s one of the most imp concept in in solid principles
How to implement Open/Closed Principle in solid principles?
The application classes should be designed in such a way that whenever fellow developers want to change the flow of control in specific conditions in application, all they need to extend the class and override some functions and that’s it.
Example - created a pojo employee with id , name. now new functionality comes which says add Training location. your constructor will fail for employees who didnt do training. better extend employee class, name it Traineed employee then add constructor.
Code Decode Playlists
Subscriber and Follow Code Decode
--------------------------------------------------------------------------------------------------------------------------------------
#solidprinciples #javainterviewquestions #codedecode
Udemy Course of Code Decode on Microservice k8s AWS CICD link:
Course Description Video :
SOLID Principles Covered with live demo. With steps on how to implement these in day to day life.
Why we need solid Principle?
The broad goal of the SOLID principles is to reduce dependencies so that engineers change one area of software without impacting others. Additionally, they’re intended to make designs easier to understand, maintain, and extend. Ultimately, using these design principles makes it easier for software engineers to avoid issues and to build adaptive, effective, and agile software.
they lead to better code for readability, maintainability, design patterns, and testability.
What are solid Principles?
The following five concepts make up our SOLID principles
Single Responsibility
Open/Closed
Liskov Substitution
Interface Segregation
Dependency Inversion
What is Single Responsibility Principle in solid principles?
It states that “One class should have one and only one responsibility”
Which specifically means - we should write, change, and maintain a class only for one purpose.
Change Class only when you need to change state of one particular object or instance
Example : POJOS follow SRP.
Suppose we have Employee and Address Class, If we want to change the state of Employee then we do not need to modify the class Account and vice-versa.
If you world have merged both as single POJO , then modification in one field for address (like state ) needs to modify and Whole POJO including Employee
Worst Design - which don’t follow SRP Hitting Database in POJO of Employee Class. That’s why we have service layer, DAP layer and Entities separated.
Why is Single Responsibility Principle IMP?
In Real world, Requirement changes and so does your code implementation to cater the changing requirement ,
The more responsibilities your class has, the more often you need to change it. To prevent frequent changes to same class,
Testing is easier - With a single responsibility, the class will have fewer test cases
Easier to Understand
Less functionality also means fewer dependencies to other classes.
So best practise says : Use layers in your application and break God classes into smaller classes or modules
What is Open/Closed Principle in solid principles?
It states that “Software components should be open for extension, but closed for modification”
The term “Open for extension” means that we can extend and include extra functionalities in our code without altering or affecting our existing implementation.
The term “Closed for modification” means that after we add the extra functionality, we should not modify the existing implementation.
In real world, You must have noticed that you change something to cater a new requirement and some other functionality breaks because of your change. To prevent that we have this principle in hand. It s one of the most imp concept in in solid principles
How to implement Open/Closed Principle in solid principles?
The application classes should be designed in such a way that whenever fellow developers want to change the flow of control in specific conditions in application, all they need to extend the class and override some functions and that’s it.
Example - created a pojo employee with id , name. now new functionality comes which says add Training location. your constructor will fail for employees who didnt do training. better extend employee class, name it Traineed employee then add constructor.
Code Decode Playlists
Subscriber and Follow Code Decode
--------------------------------------------------------------------------------------------------------------------------------------
#solidprinciples #javainterviewquestions #codedecode
0:07:04
SOLID Principles: Do You Really Understand Them?
0:15:50
Solid Design Principle Interview Questions and Answers for fresher and experienced | Code Decode
0:24:04
SOLID Principal - Interview Questions and Answers
0:19:03
1. SOLID Principles with Easy Examples | OOPs SOLID Principles Interview Question - Low Level Design
0:08:17
Software Design - Introduction to SOLID Principles in 8 Minutes
0:09:44
Solid Principles Interview Questions - You Might Get Them
0:34:44
SOLID Design Principles in java with Example | JavaTechie
0:19:09
Uncle Bob’s SOLID Principles Made Easy 🍀 - In Python!
1:01:27
Top 4 AWS (Amazon) Interview Tips around the Amazon Leadership Principles (Ex-Amazon Leader)
0:06:14
SOLID Design Principles Explained in a Nutshell
0:28:35
Learn SOLID Principles with CLEAN CODE Examples
0:41:49
SOLID Design Principles in #Angular (Advanced, 2021)
0:10:47
SOLID Design Principles with Java Examples | Clean Code and Best Practices | Geekific
0:09:05
Low Level Design 107 | Liskov Substitution Principle | 2022 | System Design
0:20:53
Learn SOLID Principles - Interview Questions
0:09:47
8 Design Patterns EVERY Developer Should Know
0:10:24
Liskov Substitution Principle Explained - SOLID Design Principles
0:11:19
SOLID principles explained | Java | System Design Interview
0:10:29
Low Level Design 105 | Single Responsibility Principle in SOLID | 2022 | System Design
0:18:23
This is the Only Right Way to Write React clean-code - SOLID
0:16:03
Solid Principles Interview Questions| Liskov substitution,Interface Segregation,Dependency Inversion
0:18:47
Software Design- Learn SOLID principles with code in 20Minutes
0:18:24
Make Your Code Clean With the SOLID Principles
0:04:12
Single Responsibility Principle Explained - SOLID Design Principles | Example Code | InterviewDOT
Комментарии