###Solid Principles
| Principle | Description |
|---|---|
| Single Responsibility | A class should have only one reason to change. (Multiple small interfaces mean fewer if statements, lower coupling, and higher cohesion.) |
| Open/Closed Principle | A class should be open for extension but closed for modification. (Use new classes for new behavior, parameters, extension methods, inheritance, dependency injection.) |
| Liskov Substitution | Objects of a superclass should be replaceable with objects of a subclass without affecting the correctness of the program. (Tell objects to perform a task instead of asking objects by using if outside the object.) |
| Interface Segregation | Clients should not be forced to depend on interfaces they do not use. (Use smaller cohesive interfaces instead of large fat interfaces.) |
| Dependency Inversion | High-level modules should not depend on low-level modules; both should depend on abstractions. |
Want to discuss cloud architecture? Find me on LinkedIn.
Found this useful? Let's go deeper.
Book a free 15-minute call to discuss your cloud, DevOps, or AI strategy challenges.