In software engineering, structural design patterns are design patterns that ease the design by identifying a simple way to realize relationships between entities.
Examples of Structural Patterns include:
Adapter pattern: 'adapts' one interface for a class into one that a client expectsAdapter pipeline: Use multiple adapters for debugging purposes.Retrofit Interface Pattern: An adapter used as a new interface for multiple classes at the same time.Aggregate pattern: a version of the Composite pattern with methods for aggregation of childrenBridge pattern: decouple an abstraction from its implementation so that the two can vary independentlyTombstone: An intermediate "lookup" object contains the real location of an object.Composite pattern: a tree structure of objects where every object has the same interfaceDecorator pattern: add additional functionality to a class at runtime where subclassing would result in an exponential rise of new classesExtensibility pattern: a.k.a. Framework - hide complex code behind a simple interfaceFacade pattern: create a simplified interface of an existing interface to ease usage for common tasksFlyweight pattern: a large quantity of objects share a common properties object to save spaceMarker pattern: an empty interface to associate metadata with a class.Pipes and filters: a chain of processes where the output of each process is the input of the nextOpaque pointer: a pointer to an undeclared or private type, to hide implementation detailsProxy pattern: a class functioning as an interface to another thing