Lesson 1
Structural design patterns
|
This module explores structural patterns, patterns that use composition to merge objects and classes into larger structures.
A good toolbox of structural patterns allows you to solve many thorny problems you are likely to encounter. They show you how to
glue different pieces of a system together in a flexible and extensible fashion. Structural patterns help you guarantee that when
one of the parts changes, the entire structure doesn't need to change. They also show you how to recast pieces that don't
fit (but that you need to use) into pieces that do fit.
In this module, you will learn:
|
- Adapter pattern: 'adapts' one interface for a class into one that a client expects
- Retrofit Interface Pattern: An adapter used as a new interface for multiple classes at the same time.
- Adapter pipeline: Use multiple adapters for debugging purposes.
- Aggregate pattern: a version of the Composite pattern with methods for aggregation of children
- Bridge pattern: decouple an abstraction from its implementation so that the two can vary independently
- Tombstone: An intermediate "lookup" object contains the real location of an object.
- Composite pattern: a tree structure of objects where every object has the same interface
- Decorator pattern: add additional functionality to a class at runtime where subclassing would result in an exponential rise of new classes
- Extensibility pattern: aka. Framework - hide complex code behind a simple interface
- Facade pattern: create a simplified interface of an existing interface to ease usage for common tasks
- Flyweight pattern: a high quantity of objects share a common properties object to save space
- Proxy pattern: a class functioning as an interface to another thing
- Pipes and filters: a chain of processes where the output of each process is the input of the next
- Private class data pattern: restrict accessor/mutator access
