Principle of Interface Segregation in Object Oriented Design (SOLID)
In a previous post we saw an introduction to SOLID Principles as a purely theoretical way. Today we will see everything about the fourth SOLID principle on the list, The Interface Segregation Principle. Let's start by giving a definition of this principle.
Definition
This principle states that a client should not be forced to implement an interface that it does not use. Stated alternatively, many client-specific interfaces are better than a general-purpose interface. If a method or function receives a dependency that implements other methods that are not of interest, a segregation must be performed and a specific interface created.
Categories
- Laravel
- Sublime Text
- OpenSSL
- PHPUnit
- Go
- Apache
- Docker
- MySQL
- OWASP
- SOLID
- JOSE
- PostgreSQL
- Static Code Analysis
- SSH
- Digital Ocean
- Java
- Javascript
- GNU/Linux Debian
- PHP
- POO
- Lenguaje C
- Lenguaje C++
- RegExp
- HTML
- Vue.js
- HTTP
- Redis
- Supervisor
- Buenas prácticas
- Ubuntu
- Webpack
- Vim
- Linux
- Arch Linux
- CSS
- Flutter
- Laravel Vapor
- CI/CD
- cPanel
- WHM
- Networking
- Python
- MacOS
- Lógica y algoritmia
- Git
- Dart
- AWS
- Codeception
- Visual Studio Code
- TypeScript
- SEO
- Node.js
- Nuxt.js
- Google Cloud