When to use Facade Method Design Pattern
- A Facade provide a simple default view of the subsystem that is good enough for most clients. Only clients needing more customizability will need to look beyond the facade.
- There are many dependencies between clients and the implementation classes of an abstraction.
- A Facade to decouple the subsystem from clients and other subsystems, thereby promoting subsystem independence and portability.
- Facade define an entry point to each subsystem level. If subsystem are dependent, then you can simplify the dependencies between them by making them communicate with each other solely through their facades.
Facade Method Design Pattern
Facade Method Design Pattern is a part of the Gang of Four design patterns and it is categorized under Structural design patterns. Before we dive deep into the details of it, imagine a building, the facade is the outer wall that people see, but behind it is a complex network of wires, pipes, and other systems that make the building function. The facade pattern is like that outer wall. It hides the complexity of the underlying system and provides a simple interface that clients can use to interact with the system.
Important Topics for the Facade Method Design Pattern
- What is the Facade Method Design Pattern?
- When to use Facade Method Design Pattern
- Key Component of Facade Method Design Pattern
- Problem Statement for the Facade Method Design Pattern
- Use Cases of Facade Method Design Pattern
- Advantages of Facade Method Design Pattern
- Disadvantages of Facade Method Design Pattern