Adaptação a Estruturas Web
Aprenda estratégias para integrar a Arquitetura Limpa a estruturas web populares (por exemplo, Spring, ASP.NET e Django) sem criar dependência delas.
Adaptação a Estruturas Web é 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.
Frameworks & Clean Architecture
Web frameworks like Spring, Django, or ASP.NET are powerful tools for building applications. But how do they fit into a Clean Architecture?
The challenge is to leverage their features without letting them dictate or couple to our core business logic. This lesson explores strategies to achieve that separation.
Avoiding Framework Coupling
Coupling occurs when one part of your code is highly dependent on another. In Clean Architecture, we want our inner layers (Entities, Use Cases) to be independent.
- If your Use Cases directly import Spring annotations or Django models, they are coupled.
- This makes it hard to change frameworks, test core logic, or reuse components.
The Dependency Rule Applied
Remember the Dependency Rule? Dependencies can only flow inwards. This is crucial for framework integration.
- Your core business logic (Entities, Use Cases) should never know about the web framework.
- The web framework (an outer layer) can and should depend on your core logic.
We need a bridge that respects this rule.
Presenters & Adapters Bridge
The 'Frameworks & Drivers' layer is where our web framework lives. To communicate with the inner 'Interface Adapters' layer (which contains Presenters and Controllers), we use specific patterns:
- Adapters: Translate incoming framework-specific requests into a format our Use Cases understand.
- Presenters: Format the output from Use Cases into a structure suitable for the web framework's views or JSON responses.
The Web Controller as an Adapter
In web applications, the framework's controller often serves as the primary adapter. Its job is to:
- Receive HTTP requests (e.g., from a browser or API client).
- Extract relevant data from the request.
- Convert this data into a simple object (a Request Model) that matches the Use Case's Input Port.
- Call the Use Case.
- Receive output from the Use Case (a Response Model).
- Pass this output to a Presenter to format the final HTTP response.
Defining an Input Port
Our Use Cases expose simple interfaces, called Input Ports. The web controller will depend on this interface, not the concrete Use Case implementation. This keeps the Use Case truly independent.
Here's an example of an Input Port and its corresponding Request object:
interface AddItemInputPort {
void execute(AddItemRequest request);
}
class AddItemRequest {
public final String itemName;
public final double price;
public AddItemRequest(String itemName, double price) {
this.itemName = itemName;
this.price = price;
}
}
public class Main {
public static void main(String[] args) {
// These are just definitions, not runnable logic on their own.
// We'll see them in action soon!
System.out.println("InputPort and Request defined.");
}
}Implementing a Use Case
The actual business logic resides within the Use Case. It implements the AddItemInputPort and performs the operation, completely unaware of how it was invoked (e.g., by a web request, a CLI, or a message queue).
interface AddItemInputPort {
void execute(AddItemRequest request);
}
class AddItemRequest {
public final String itemName;
public final double price;
public AddItemRequest(String itemName, double price) {
this.itemName = itemName;
this.price = price;
}
}
class AddItemUseCase implements AddItemInputPort {
@Override
public void execute(AddItemRequest request) {
System.out.println("Use Case: Processing item '" +
request.itemName + "' with price $" +
request.price + ".");
// In a real application, this would involve business rules,
// interacting with entities, and potentially repositories.
}
}
public class Main {
public static void main(String[] args) {
AddItemInputPort useCase = new AddItemUseCase();
AddItemRequest request = new AddItemRequest("Fancy Pen", 15.75);
useCase.execute(request);
}
}Web Controller Adapter in Action
Now, let's see how a simplified web controller (acting as an adapter) uses our Use Case. Notice it only interacts with the AddItemInputPort interface, not the concrete AddItemUseCase class.
interface AddItemInputPort {
void execute(AddItemRequest request);
}
class AddItemRequest {
public final String itemName;
public final double price;
public AddItemRequest(String itemName, double price) {
this.itemName = itemName;
this.price = price;
}
}
class AddItemUseCase implements AddItemInputPort {
@Override
public void execute(AddItemRequest request) {
System.out.println("Use Case processed: " + request.itemName);
}
}
// This class simulates a web framework controller
class WebFrameworkController {
private final AddItemInputPort addItemInputPort;
// Controller depends on the Input Port interface
public WebFrameworkController(AddItemInputPort addItemInputPort) {
this.addItemInputPort = addItemInputPort;
}
// This method simulates handling an HTTP POST request
public String handleHttpRequest(String name, double cost) {
System.out.println("Controller received HTTP request for: " + name);
AddItemRequest request = new AddItemRequest(name, cost);
addItemInputPort.execute(request); // Delegate to Use Case
return "HTTP Response: Item '" + name + "' added.";
}
}
public class Main {
public static void main(String[] args) {
// Setup: Inject the Use Case into the Controller
AddItemInputPort useCase = new AddItemUseCase();
WebFrameworkController controller = new WebFrameworkController(useCase);
// Simulate an incoming web request
String response = controller.handleHttpRequest("Notebook", 8.99);
System.out.println(response);
}
}Benefits of Decoupling Frameworks
This adapter-based approach offers significant advantages:
- Testability: Use Cases can be tested in isolation, without needing to boot up the entire web framework.
- Maintainability: Changes or upgrades to your web framework have minimal impact on your core business logic.
- Flexibility: You could swap out your web framework for another (e.g., from Spring to JAX-RS) with changes only in the outer 'Frameworks & Drivers' layer.
- Framework Independence: Your valuable business rules are not tied to a specific technology vendor.
Check Your Understanding
Which of the following best describes the role of a web controller when integrating a Clean Architecture application with a web framework?
Recap: Framework Integration
In this lesson, we explored how to integrate web frameworks into a Clean Architecture application while maintaining crucial separation:
- We treat the web framework as an outer layer that depends on our core logic, not the other way around.
- Controllers in the web framework act as adapters, translating web requests into Use Case Input Ports and formatting Use Case output.
- This approach ensures high testability, maintainability, and framework independence for your core application.
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 “Adaptação a Estruturas Web” é grátis?
Sim — o texto completo de “Adaptação a Estruturas Web” é 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 “Adaptação a Estruturas Web”?
Aprenda estratégias para integrar a Arquitetura Limpa a estruturas web populares (por exemplo, Spring, ASP.NET e Django) sem criar dependência delas. 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 “Adaptação a Estruturas Web”?
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
- Apresentadores e Modelos de Visualização
- Adaptação a Estruturas Web
- Testando a Camada de Apresentação
- Objetos Humildes e o Limite da Visão