Scribd
Upload
3 views

# Decorator Pattern

Decorator Pattern

Uploaded by

Carlos Renato
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
3 views

# Decorator Pattern

Decorator Pattern

Uploaded by

Carlos Renato
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 1

# Decorator Pattern

- A Decorator wraps another object to extend its responsabilities, without


modifying its existing behavior, while keeping the same signature of public
methods.
- Decorators are used to add orthogonal responsibilities like logging, caching and
retrying.
- The Decorator pattern is useful when you want to add behavior to an existing
component but either cannot or do not want to modify the source code.
- This is typically done to adhere to the single responsibility principle (SRP)
to keep our code clean, readable, and maintainable.

- Some real-world use cases for the decorator design pattern include:
- Execution policies, such as exception handling, retrying, or caching, which
help improve the performance and reliability of your apps.
- Observability, for instance, by adding logging to all calls to an external
component.
- User Interface, like adding a scrollbar to a large textbox. Another example is
the Adorner concept in WPF.
- Streams, with features such as buffering, encryption, or compression.
- Use Cases for the Decorator Pattern
- Extending Functionality: When you have a base component with basic
functionality, but you need to add additional features or behaviors to it
dynamically without altering its structure. Decorators allow you to add new
responsibilities to objects at runtime.
- Multiple Combinations of Features: When you want to provide multiple
combinations of features or options to an object. Decorators can be stacked and
combined in different ways to create customized variations of objects, providing
flexibility to users.
- Legacy Code Integration: When working with legacy code or third-party libraries
where modifying the existing codebase is not feasible or desirable, decorators can
be used to extend the functionality of existing objects without altering their
implementation.
- GUI Components: In graphical user interface (GUI) development, decorators can
be used to add additional visual effects, such as borders, shadows, or animations,
to GUI components like buttons, panels, or windows.
- Input/Output Streams: Decorators are commonly used in input/output stream
classes in languages like Java. They allow you to wrap streams with additional
functionality such as buffering, compression, encryption, or logging without
modifying the original stream classes.
</br>

# Real World Example

- https://dofactory.com/net/decorator-design-pattern

Example of Decorator Design Pattern


- https://www.geeksforgeeks.org/decorator-pattern/
- Below is the problem statement to understand the Decorator Design Pattern:

- Suppose we are building a coffee shop application where customers can order
different types of coffee. Each coffee can have various optional add-ons such as
milk, sugar, whipped cream, etc. We want to implement a system where we can
dynamically add these add-ons to a coffee order without modifying the coffee
classes themselves.

You might also like