Many times in software development we across a situation where we have to make architectural decisions which affects the existing structure of a class.
Structural pattern comes into picture in this moment.
After a lot of writing finally all structural patterns are now ready to read and understand.
- Adapter Pattern - creates a wrapper around an existing class and makes it compatible with another class.
- Composite Pattern - Let the clients treat individual objects and compositions of objects uniformly
- Decorator Pattern - Attach additional responsibilities to an object dynamically.
- Facade Pattern - Provides a unified interface to a set of interfaces in a subsystem.
- Flyweight Pattern - Used when one instance of a class can be used to provide many virtual instances.
- Bridge Pattern - Bridge Pattern decouple an abstraction from its implementation so that the two can vary independently
- Proxy Pattern - Proxy Pattern Provide a surrogate or placeholder for another object to control access to it
(I am about to start a online training for design patterns and other technical stuffs, you can contact me at 9870148461 or at SukeshMarla@Gmail.com)