Clean Architecture & Design Patterns in Practice · 课时

适配器与装饰器模式

理解适配器如何让不兼容的接口协同工作，以及装饰器如何动态添加职责。

第 1 / 4 课12 个步骤

适配器与装饰器模式 是 CoddyKit 上的免费 Clean Architecture & Design Patterns in Practice 课时。这是第 1 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 Clean Architecture & Design Patterns in Practice 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Clean Architecture & Design Patterns in Practice 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

Structural Patterns: Connect & Enhance

Welcome to Structural Design Patterns! These patterns help you compose objects and classes into larger structures, making systems more flexible and efficient.

In this lesson, we'll explore two powerful patterns:

Adapter Pattern: For making incompatible interfaces work together.
Decorator Pattern: For adding new functionalities to objects dynamically.

The Incompatibility Challenge

Imagine you have an existing system that expects objects to behave in a certain way (a specific interface). Now, you need to integrate a new component that does similar work but has a different interface.

How do you make them talk without changing the existing system or the new component? This is a common challenge in software development.

Meet the Adapter Pattern

The Adapter Pattern acts as a bridge between two incompatible interfaces. It converts the interface of one class into another interface that clients expect.

Think of a universal power adapter: it lets your device (client) plug into any wall socket (adaptee) by converting the physical connection. The device doesn't care about the socket type, only that it gets power.

Roles in the Adapter Pattern

The Adapter Pattern involves three key roles:

Target: The interface the client expects and uses.
Adaptee: The existing class with the incompatible interface that needs adapting.
Adapter: The class that implements the Target interface and wraps an Adaptee instance, translating client requests into calls to the Adaptee.

It allows clients to work with different classes through a single, consistent interface.

Adapter Code Example

Let's see how an adapter can make a modern console writer work with an old logging system.

Our LegacyLogger expects a logMessage method, but our ModernConsoleWriter has writeToConsole.

The ConsoleWriterAdapter bridges this gap.

interface LegacyLogger {
  void logMessage(String message);
}

class ModernConsoleWriter {
  public void writeToConsole(String text) {
    System.out.println("Console: " + text);
  }
}

class ConsoleWriterAdapter implements LegacyLogger {
  private ModernConsoleWriter adaptee;

  public ConsoleWriterAdapter(ModernConsoleWriter adaptee) {
    this.adaptee = adaptee;
  }

  @Override
  public void logMessage(String message) {
    adaptee.writeToConsole("[LEGACY] " + message);
  }
}

public class Main {
  public static void main(String[] args) {
    ModernConsoleWriter writer = new ModernConsoleWriter();
    LegacyLogger logger = new ConsoleWriterAdapter(writer);

    System.out.println("Using the adapter:");
    logger.logMessage("This is an old log entry.");

    System.out.println("\nUsing the original writer directly:");
    writer.writeToConsole("This is a modern console output.");
  }
}

When to Apply Adapter

Consider using the Adapter Pattern when:

You want to use an existing class, but its interface doesn't match the one you need.
You want to create a reusable class that cooperates with unrelated or unforeseen classes, meaning classes that don't necessarily have compatible interfaces.
You're integrating a new component or library into an existing system with a fixed API.

Decorator: Adding Features Dynamically

Sometimes you need to add new responsibilities or behaviors to an object without altering its original structure or affecting other objects of the same class. This is where the Decorator Pattern shines.

It allows you to wrap objects with new functionality, like adding toppings to a base coffee. Each topping (decorator) adds a new cost and description without changing the coffee itself.

Roles in the Decorator Pattern

The Decorator Pattern involves:

Component: The base interface for objects that can be decorated. Both concrete components and decorators implement this.
Concrete Component: The basic object to which responsibilities can be added.
Decorator: An abstract class (or interface) that maintains a reference to a Component object and implements the Component interface.
Concrete Decorators: Specific decorators that add new functionalities to the component.

Decorator Code Example

Let's see how to add milk and sugar to a simple coffee using decorators. Each decorator wraps the existing coffee object and adds its own logic.

This allows for flexible combinations of enhancements.

interface Coffee {
  double getCost();
  String getDescription();
}

class SimpleCoffee implements Coffee {
  @Override
  public double getCost() {
    return 2.0;
  }

  @Override
  public String getDescription() {
    return "Simple Coffee";
  }
}

abstract class CoffeeDecorator implements Coffee {
  protected Coffee decoratedCoffee;

  public CoffeeDecorator(Coffee coffee) {
    this.decoratedCoffee = coffee;
  }

  @Override
  public double getCost() {
    return decoratedCoffee.getCost();
  }

  @Override
  public String getDescription() {
    return decoratedCoffee.getDescription();
  }
}

class MilkDecorator extends CoffeeDecorator {
  public MilkDecorator(Coffee coffee) {
    super(coffee);
  }

  @Override
  public double getCost() {
    return super.getCost() + 0.5;
  }

  @Override
  public String getDescription() {
    return super.getDescription() + ", Milk";
  }
}

class SugarDecorator extends CoffeeDecorator {
  public SugarDecorator(Coffee coffee) {
    super(coffee);
  }

  @Override
  public double getCost() {
    return super.getCost() + 0.2;
  }

  @Override
  public String getDescription() {
    return super.getDescription() + ", Sugar";
  }
}

public class Main {
  public static void main(String[] args) {
    Coffee myCoffee = new SimpleCoffee();
    System.out.println(myCoffee.getDescription() + " $" + myCoffee.getCost());

    myCoffee = new MilkDecorator(myCoffee);
    System.out.println(myCoffee.getDescription() + " $" + myCoffee.getCost());

    myCoffee = new SugarDecorator(myCoffee);
    System.out.println(myCoffee.getDescription() + " $" + myCoffee.getCost());

    Coffee anotherCoffee = new SugarDecorator(new MilkDecorator(new SimpleCoffee()));
    System.out.println(anotherCoffee.getDescription() + " $" + anotherCoffee.getCost());
  }
}

When to Apply Decorator

Use the Decorator Pattern when:

You need to add responsibilities to individual objects dynamically and transparently, without affecting other objects.
You want to extend an object's functionality without using subclassing, which can lead to a "subclass explosion" for many combinations.
You need to allow for flexible combinations of responsibilities.

Quick Check: Pattern Purpose

Read the descriptions below. Which one correctly identifies the primary purpose of the Adapter Pattern?

在交互式课程中回答

Recap: Adapter & Decorator

Great job! You've now learned two powerful structural design patterns:

Adapter Pattern: Solves the problem of incompatible interfaces, allowing existing components to work together seamlessly. It's about 'making things fit'.
Decorator Pattern: Solves the problem of adding new responsibilities to objects dynamically, without altering their core structure. It's about 'enhancing functionality'.

These patterns provide flexible ways to structure your code, making it more maintainable and extensible. Keep practicing them!

免费开始

用 AI 导师学习 Clean Architecture & Design Patterns in Practice — 免费

在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。

课程: 12
课程: 48

免费开始学习查看完整课程

常见问题解答

「适配器与装饰器模式」课时是免费的吗？

是的 — 「适配器与装饰器模式」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Clean Architecture & Design Patterns in Practice 课程的其余内容，请升级到 CoddyKit PRO。 Clean Architecture & Design Patterns in Practice 课程共包含 4 节课。

「适配器与装饰器模式」这节课中我会学到什么？

理解适配器如何让不兼容的接口协同工作，以及装饰器如何动态添加职责。你通过在浏览器中直接运行的动手代码来练习 Clean Architecture & Design Patterns in Practice，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 Clean Architecture & Design Patterns in Practice 需要有经验吗？

无需任何先前经验。CoddyKit 上的 Clean Architecture & Design Patterns in Practice 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 1 节课，共 4 节。

「适配器与装饰器模式」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 Clean Architecture & Design Patterns in Practice 课中编写并运行代码吗？

能。每节 Clean Architecture & Design Patterns in Practice 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 Clean Architecture & Design Patterns in Practice