Segregação de Interfaces na Prática
Aplique o Princípio da Segregação de Interfaces para criar interfaces enxutas e específicas, evitando interfaces extensas que obriguem os clientes a depender de métodos que não utilizam.
Segregação de Interfaces na Prática é uma aula grátis de Clean Architecture & Design Patterns in Practice no CoddyKit. Esta é a aula 2 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Clean Architecture & Design Patterns in Practice, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Clean Architecture & Design Patterns in Practice inclui 4 aulas no total.
Partes desta aula ainda não foram traduzidas e aparecem em inglês.
What is ISP?
Welcome to the Interface Segregation Principle (ISP)! This principle is one of the five SOLID principles of object-oriented design.
At its core, ISP states that clients should not be forced to depend on interfaces they do not use. In simpler terms, don't make classes implement methods they don't need.
The Problem: Fat Interfaces
A 'fat interface' is an interface that contains too many methods, some of which are irrelevant to certain classes that implement it.
When a class implements a fat interface, it's forced to provide implementations for all methods, even those it doesn't use. This often leads to empty or placeholder method bodies, which is a code smell.
Fat Interface Example
Consider a general IWorker interface. While a human worker might perform all these actions, a robot worker might not eat or sleep. Let's see how this creates issues.
interface IWorker {
void work();
void eat();
void sleep();
void manageTeam();
}
class Robot implements IWorker {
@Override
public void work() {
System.out.println("Robot working...");
}
@Override
public void eat() {
// Robots don't eat, forced to implement
System.out.println("Robot can't eat.");
}
@Override
public void sleep() {
// Robots don't sleep, forced to implement
System.out.println("Robot can't sleep.");
}
@Override
public void manageTeam() {
// Not all robots manage teams
System.out.println("Robot can't manage team.");
}
}
public class Main {
public static void main(String[] args) {
Robot robot = new Robot();
robot.work();
robot.eat(); // This call is meaningless for a robot
}
}Consequences of Fat Interfaces
As seen with the Robot example, implementing a fat interface leads to several problems:
- Code Smells: Empty or placeholder method implementations.
- Brittle Code: Changes to an interface (e.g., adding a new method) might force unrelated clients to update their code.
- Reduced Cohesion: The interface has too many responsibilities, making it less focused.
- Increased Coupling: Clients are coupled to methods they don't use, making the system harder to maintain and test.
Solution: Segregating Interfaces
The Interface Segregation Principle proposes splitting large, 'fat' interfaces into smaller, more specific ones.
Each client (class) then only implements the interfaces that are relevant to its specific responsibilities. This ensures clients are not forced to depend on methods they don't need.
ISP in Action: Refactored Code
Let's refactor our IWorker example by creating smaller, role-specific interfaces. Now, each worker type can implement only what it truly needs.
interface IWorkable {
void work();
}
interface IEatable {
void eat();
}
interface ISleepable {
void sleep();
}
interface IManager extends IWorkable { // Managers also work
void manageTeam();
}
class HumanWorker implements IManager, IEatable, ISleepable {
@Override
public void work() { System.out.println("Human working..."); }
@Override
public void eat() { System.out.println("Human eating..."); }
@Override
public void sleep() { System.out.println("Human sleeping..."); }
@Override
public void manageTeam() { System.out.println("Human managing team..."); }
}
class RobotWorker implements IWorkable { // Only works
@Override
public void work() { System.out.println("Robot working..."); }
}
public class Main {
public static void main(String[] args) {
HumanWorker human = new HumanWorker();
human.work();
RobotWorker robot = new RobotWorker();
robot.work();
// robot.eat(); // This would now be a compile error, as expected!
}
}Benefits of Using ISP
Applying ISP brings significant advantages to your software design:
- Improved Cohesion: Interfaces become more focused and represent a single, clear responsibility.
- Reduced Coupling: Clients depend only on the specific methods they require, leading to looser coupling.
- Easier Maintenance: Changes to one interface don't impact clients that don't implement it.
- Better Testability: Smaller, focused interfaces are easier to mock and test in isolation.
- Flexibility: New functionalities can be added by creating new interfaces or extending existing small ones without affecting existing clients.
ISP in Practice
ISP is particularly useful in systems with diverse client types or complex functionalities:
- Role-Based Systems: Different user roles (e.g., Administrator, Editor, Viewer) might interact with different parts of a system, each needing a specific interface.
- API Design: When designing APIs, provide specific endpoints or interfaces for different client applications (e.g., mobile apps vs. web apps).
- Plugin Architectures: Plugins can implement only the specific interfaces that define the functionalities they provide to the main application.
ISP vs. SRP: A Quick Look
While both ISP and the Single Responsibility Principle (SRP) promote focused design, they operate at different levels:
- SRP (Single Responsibility Principle): Focuses on classes, stating a class should have only one reason to change.
- ISP (Interface Segregation Principle): Focuses on interfaces and clients, ensuring clients aren't forced to depend on methods they don't use.
They often work hand-in-hand. Applying SRP to classes might naturally lead to clearer interfaces, and applying ISP can help classes better adhere to SRP by only implementing what's truly relevant to their single responsibility.
Check Your Understanding
Given an interface IDocumentProcessor with methods printDocument(), scanDocument(), faxDocument(), and copyDocument(), which of the following are good ways to apply the Interface Segregation Principle?
Lesson Summary
Great job! You've learned about the Interface Segregation Principle:
- Clients should not be forced to depend on interfaces they do not use.
- 'Fat interfaces' lead to irrelevant method implementations and brittle code.
- ISP solves this by splitting large interfaces into smaller, client-specific ones.
- This improves cohesion, reduces coupling, and makes code more maintainable and testable.
Keep these principles in mind to design more robust and flexible software!
Aprenda Clean Architecture & Design Patterns in Practice com um tutor de IA — grátis
Escreva e execute código real no seu navegador, obtenha ajuda instantânea de um tutor de IA 24/7 e continue de onde parou na web ou no app.
- Cursos
- 12
- Aulas
- 48
Perguntas Frequentes
A aula “Segregação de Interfaces na Prática” é grátis?
Sim — o texto completo de “Segregação de Interfaces na Prática” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Clean Architecture & Design Patterns in Practice, atualize para CoddyKit PRO. O curso de Clean Architecture & Design Patterns in Practice inclui 4 aulas no total.
O que vou aprender em “Segregação de Interfaces na Prática”?
Aplique o Princípio da Segregação de Interfaces para criar interfaces enxutas e específicas, evitando interfaces extensas que obriguem os clientes a depender de métodos que não utilizam. Você pratica Clean Architecture & Design Patterns in Practice com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.
Preciso ter experiência prévia para começar Clean Architecture & Design Patterns in Practice?
Nenhuma experiência prévia é necessária. Clean Architecture & Design Patterns in Practice no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 2 de 4.
Quanto tempo leva a aula “Segregação de Interfaces na Prática”?
A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.
Posso escrever e executar código nesta aula de Clean Architecture & Design Patterns in Practice?
Sim. Cada aula de Clean Architecture & Design Patterns in Practice inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.
Todas as aulas deste curso
- Aprofundamento na Inversão de Dependência
- Segregação de Interfaces na Prática
- Refatoração com Padrões de Projeto
- Domínio da Responsabilidade Única e do Aberto-Fechado