Single responsibility principle is part of SOLID principles. Single responsibility principle is the first principle of all Solid Principles. Single-responsibility Principle (SRP) states that a class should have one and only one reason to change, meaning that a class should have only one job. ** Where to use Single Responsibility Principle ** 1. Use single responsibility principle if you a class, or a method or any microservice doing multiple jobs. 2. Use single responsibility principle whenever you want to simplify your code. 3. Use single responsibility principle whenever you want to make your code simple, easy to understand, easy to read and easy to maintain. 4. Use single responsibility principle if your project is growing faster and bigger and you feel any modification in a class would break other functionality.
** Advantages of Single Responsibility Principle ** 1. Single Responsibility Principle makes your software easier to implement and prevents unexpected side-effects of future changes. 2. Using SRP Classes, software components and microservices that have only one responsibility are much easier to explain, understand and implement than the ones that provide a solution for everything.
** Solid Principles Introduction ** Eventually, as our applications grow in size so as the complexity hence, we need SOLID principle to reduce the complexity and to maintain an application. These principles establish practices that lend to developing software with considerations for maintaining and extending as the project grows. Adopting these practices can also contribute to avoiding code smells, refactoring code, and Agile or Adaptive software development. The SOLID Principles are five principles of Object-Oriented class design. They are a set of rules and best practices to follow while designing a class structure. ** Solid Principles & Object-Oriented Programming ** In software development, Object-Oriented Design plays a crucial role when it comes to writing flexible, scalable, maintainable, and reusable code. There are so many benefits of using OOD but every developer should also have the knowledge of the SOLID principle for good object-oriented design in programming.
** Chapter Timestamps ** 0:00 Welcome to Single Responsibility Principle 1:12 Agenda of the video 2:09 Introduction to Single Responsibility Principle 3:48 Real world example of Single Responsibility Principle 4:42 Java code example of Single Responsibility Principle 7:45 Where to use Single Responsibility Principle 8:25 Benefits of Single Responsibility Principle 8:53 Summary of Single Responsibility Principle 9:32 Next video on Open-Closed Principle
** Acronyms ** OOP – Object Oriented Programming Languages SRP – Single Responsibility Principle OCP – Open Closed Principle LSP – Liskov Substitution Principle ISP – Interface Segregation Principle DIP – Dependency Inversion Principle COD – Code One Digest
** ABOUT OUR CHANNEL ** CodeOneDigest is a youtube channel that produces videos on programming languages, cloud and container technologies, Software design principles, Java frameworks in English and Hindi languages.
