0Pricing
Clean Architecture & Design Patterns in Practice · 강의

어댑터와 데코레이터 패턴

어댑터로 호환되지 않는 인터페이스를 함께 작동하게 만드는 방법과 데코레이터로 책임을 동적으로 추가하는 방법을 이해합니다.

어댑터와 데코레이터 패턴은(는) CoddyKit의 무료 Clean Architecture & Design Patterns in Practice 강의입니다. 이것은 4개 중 1번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 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!

자주 묻는 질문

“어댑터와 데코레이터 패턴” 강의는 무료인가요?

네 — “어댑터와 데코레이터 패턴” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 Clean Architecture & Design Patterns in Practice 강의 전체를 잠금 해제할 수 있습니다. Clean Architecture & Design Patterns in Practice 강의에는 총 4개의 강의가 포함되어 있습니다.

“어댑터와 데코레이터 패턴”에서 뭘 배우나요?

어댑터로 호환되지 않는 인터페이스를 함께 작동하게 만드는 방법과 데코레이터로 책임을 동적으로 추가하는 방법을 이해합니다. 브라우저에서 직접 실행하는 실습 코드로 Clean Architecture & Design Patterns in Practice을(를) 배우며, 24/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

Clean Architecture & Design Patterns in Practice을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 Clean Architecture & Design Patterns in Practice은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 1번째 강의입니다.

“어댑터와 데코레이터 패턴” 강의는 얼마나 걸리나요?

대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.

이 Clean Architecture & Design Patterns in Practice 강의에서 코드를 작성하고 실행할 수 있나요?

네. 모든 Clean Architecture & Design Patterns in Practice 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.

이 강의의 모든 강의

  1. 어댑터와 데코레이터 패턴
  2. 퍼사드와 프록시 패턴
  3. 컴포지트와 브리지 패턴
  4. 메모리 효율을 위한 Flyweight 패턴
← Clean Architecture & Design Patterns in Practice(으)로 돌아가기