0Pricing
Clean Architecture & Design Patterns in Practice · Aula

Padrões Método Template e Estado

Defina esqueletos de algoritmos com o Método Template e permita que objetos alterem seu comportamento com o Estado.

Padrões Método Template e Estado é uma aula grátis de Clean Architecture & Design Patterns in Practice no CoddyKit. Esta é a aula 3 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.

Behavioral Patterns Focus

Welcome back! In this lesson, we'll dive into two powerful behavioral design patterns: the Template Method and the State patterns.

These patterns help manage algorithms and object behavior in flexible ways, making your code easier to extend and maintain.

What is Template Method?

The Template Method pattern defines the skeleton of an algorithm in an operation, deferring some steps to subclasses.

It lets subclasses redefine certain steps of an algorithm without changing the algorithm's overall structure.

Algorithm Skeleton

Imagine a recipe with fixed steps, but some ingredients or cooking times can vary. The core "how-to" is set, but details are flexible.

  • An abstract class defines the overall algorithm with a final "template method."
  • This method calls a series of primitive operations (abstract methods) that subclasses must implement.
  • It can also include concrete methods (shared steps) and hook methods (optional steps).

Template Method in Action

Let's consider making beverages. Both coffee and tea require boiling water and pouring into a cup. But brewing and adding condiments differ.

The Template Method allows us to define the common steps once, while allowing specific beverage classes to customize their unique steps.

Beverage Maker Example

Here's how we can implement a generic BeverageMaker using the Template Method. Notice the prepareBeverage() method is final, fixing the algorithm.

public abstract class BeverageMaker {

  // The template method - defines the algorithm's skeleton
  public final void prepareBeverage() {
    boilWater();
    brew();
    pourInCup();
    addCondiments();
  }

  // Common steps
  private void boilWater() {
    System.out.println("Boiling water");
  }

  private void pourInCup() {
    System.out.println("Pouring into cup");
  }

  // Abstract steps - must be implemented by subclasses
  protected abstract void brew();
  protected abstract void addCondiments();
}

public class CoffeeMaker extends BeverageMaker {
  @Override
  protected void brew() {
    System.out.println("Dripping coffee through filter");
  }

  @Override
  protected void addCondiments() {
    System.out.println("Adding sugar and milk");
  }
}

public class TeaMaker extends BeverageMaker {
  @Override
  protected void brew() {
    System.out.println("Steeping the tea bag");
  }

  @Override
  protected void addCondiments() {
    System.out.println("Adding lemon");
  }
}

public class Main {
  public static void main(String[] args) {
    System.out.println("--- Making Coffee ---");
    BeverageMaker coffee = new CoffeeMaker();
    coffee.prepareBeverage();

    System.out.println("\n--- Making Tea ---");
    BeverageMaker tea = new TeaMaker();
    tea.prepareBeverage();
  }
}

What is the State Pattern?

The State pattern allows an object to alter its behavior when its internal state changes. It appears as if the object has changed its class.

Instead of using many if/else or switch statements, you encapsulate each state's behavior into a separate class.

Context and States

Think of a traffic light. Its behavior (what light is active) changes based on its current state (Red, Yellow, Green).

  • The Context class holds a reference to a State object and delegates state-specific behavior to it.
  • The State Interface declares methods for state-specific behaviors.
  • Concrete State classes implement the State Interface, providing behavior for a particular state.

Traffic Light States

A TrafficLight object doesn't have complex logic itself. Instead, it holds a reference to its current LightState (e.g., RedLightState, GreenLightState).

When an event occurs (like a timer tick), the TrafficLight delegates the action to its current LightState object, which then handles the transition to the next state.

Traffic Light Simulation

Here’s a simple traffic light simulation using the State pattern. The TrafficLight context changes its internal LightState object, which dictates its behavior.

// State Interface
interface LightState {
  void handleRequest(TrafficLight light);
  String getStateName();
}

// Concrete State: Red Light
class RedLightState implements LightState {
  @Override
  public void handleRequest(TrafficLight light) {
    System.out.println("Red light: STOP!");
    light.setState(new GreenLightState()); // Transition to Green
  }

  @Override
  public String getStateName() {
    return "Red";
  }
}

// Concrete State: Green Light
class GreenLightState implements LightState {
  @Override
  public void handleRequest(TrafficLight light) {
    System.out.println("Green light: GO!");
    light.setState(new YellowLightState()); // Transition to Yellow
  }

  @Override
  public String getStateName() {
    return "Green";
  }
}

// Concrete State: Yellow Light
class YellowLightState implements LightState {
  @Override
  public void handleRequest(TrafficLight light) {
    System.out.println("Yellow light: CAUTION!");
    light.setState(new RedLightState()); // Transition to Red
  }

  @Override
  public String getStateName() {
    return "Yellow";
  }
}

// Context
class TrafficLight {
  private LightState currentState;

  public TrafficLight() {
    // Initial state
    this.currentState = new RedLightState();
  }

  public void setState(LightState state) {
    this.currentState = state;
  }

  public void change() {
    System.out.print("Current state: " + currentState.getStateName() + " -> ");
    currentState.handleRequest(this);
  }
}

public class Main {
  public static void main(String[] args) {
    TrafficLight light = new TrafficLight();

    // Simulate light changes
    light.change(); // Red -> Green
    light.change(); // Green -> Yellow
    light.change(); // Yellow -> Red
    light.change(); // Red -> Green
  }
}

Pattern Identification

You are designing a document processing system where different document types (PDF, DOCX, TXT) share a common conversion process to HTML, but each has unique steps for parsing its content.

Which design pattern would best suit defining the overall conversion process while allowing specific parsing steps to vary?

Summary of Patterns

Great job! You've learned about two powerful behavioral patterns:

  • The Template Method pattern allows you to define a fixed algorithm structure while letting subclasses implement specific steps.
  • The State Pattern enables an object to change its behavior based on its internal state, encapsulating state-specific logic into separate classes.

These patterns boost flexibility and maintainability in your designs!

Perguntas Frequentes

A aula “Padrões Método Template e Estado” é grátis?

Sim — o texto completo de “Padrões Método Template e Estado” é 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 “Padrões Método Template e Estado”?

Defina esqueletos de algoritmos com o Método Template e permita que objetos alterem seu comportamento com o Estado. 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 3 de 4.

Quanto tempo leva a aula “Padrões Método Template e Estado”?

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

  1. Padrões Observador e Estratégia
  2. Padrões Comando e Iterador
  3. Padrões Método Template e Estado
  4. Mediador e cadeia de responsabilidades
← Voltar para Clean Architecture & Design Patterns in Practice