S.O.L.I.D Principles

-

S.O.L.I.D Principles Introduction

  •  SOLID principles are the look principle that allows us to manage most of the software design problems. 
  • The principles are a subset of many principles by Robart C Martin

S.O.L.I.D are 5 object-oriented principles that should be followed when design software 
  • S-  Single Responsibility Principle (SRP)
  • O- Open- Closed Principle (OCP)
  • L- Liskov Substitution Principle (LSP)
  • I - Interface Segregation Principle (ISP)
  • D- Dependency Inversion Principle (DIP)

Single Responsibility Principle (SRP)


And that responsibility should be entirely encapsulated by the class every module or class should have responsibility for one part of the functionality provided by the software
 





Open-Closed Principle (OCP)

Adding new classes, attributes, and methods, instead of changing the current ones or existing ones should implement any new functionality. Bertrand Meyer originated the term OCP.    

Why OCP?

if not followed 
  •    End up testing the entire functionality.
  •    QA term needs to test the entire now.
  •    Costly process for the origination. 
  •    Breaks the single responsibility as well. 
  •    Maintenance overheads increase on the classes.  

Liskov Substitution Principle(LSP)

Barbara Liskov introduced the concept of this principle in a 1987 conference. Formal definition created by Barbara Liskov and Jeannette wing in 1994. LSP is a subtyping relation, called (strong) behavioral subtyping. Extension of the Open Close Principle. Any subclass replacing parent class instantiation is not always fulfilling LSP  




Interface Segregation Principle (ISP)

One fat interface need to be split too much smaller and relevant interface so that clients can know about the interfaces that are relevant to them. 






 Dependency Inversion Principle (DIP)

  • High-level modules should not depend on low-level modules. Both should depend on abstractions
  • Abstractions should not depend on details. Details should depend on abstractions.

The interaction between low level and high-level modules should be thought of as an abstract interaction between them

Intention of usage

















Comments

Post a Comment

Popular posts from this blog

HTTP Methods

-
Image
  What is HTTP Verb? HTTP verbs are technically correct terms of request, and it communicates the action a user intends to take on specific resources related to these verbs and methods. HTTP password processing is very common. GET, POST, PUT, PATCH, DELETE, OPTIONS, and HEAD are the key HTTP most commonly used verbs used with RESTful services. HTTP GET The GET request was used to obtain information on resources and is not subject to any other means. The GET API should be malicious. This simply means that every API that makes similar requests should return the same result until the resource status of the server is changed. GET requests are made securely because they do not change the status of the resource. Example URI - HTTP GET http://www.abc.com/users HTTP POST  The HTTP POST method is used to create relevant resources. POST request methods are insecure. In this case, when two similar post requests are made, there may be two different resources related to the same informatio...
Read more

KoaJS in NodeJS

-
Image
What is KOA? Widely used server-side framework for Node.js. Koa was created by the same creators of express, another popular backend Jawa Script framework Koa provides a minimal interface for developing apps and APIs Accordingly, the creators sought to take into account all the shortcomings of the predecessor and make it more  modern and convenient  to use Extremely Lightweight Smaller footprint than any other Node.js framework including Express. Better and Thinner middleware. You have the option to extend the framework with an added module Modern Framework Koa is Built ES6+ and promotes modern JavaScript syntax Uses generators and async /await. Helps devs create apps that remain relevant over a long period of time Request and Response Koa uses a req and res object on top of the standard vanilla JS request and the response It accelerates HTTP server development by providing additional functionality Encapsulates req/res into a single object using context. This helps devs build ...
Read more