Facade Pattern

Applicability

• You want to provide a simple interface to a complex subsystem.Subsystems often get more complex as they evolve. Most patterns, when applied, result in more and smaller classes. This makes the subsystem more reusable and easier to customize, but it also becomes harder to use for clients that don't need to customize it. A facade can 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. Introduce a facade to decouple the subsystem from clients and other subsystems, thereby promoting subsystem independence and portability
• You want to layer your subsystems. Use a facade to define an entry point to each subsystem level. If subsystems are dependent, then you can simplify the dependencies between them by making them communicate with each other solely through their facades

#DesignPatterns

Let's code up a real simple application that provide a simple facade interface to talk to different subsystems underneath. First of, we would like to define three simple structs namely React, Vue and Angular like so

And next we would finish up by provide a simple interface for client code talk to different subsystems

There we have it, the Facade Pattern implemented in Go. With this pattern, the client code is absolutely unaware of the complexity goes behind the scene by large amount of subsystems - similar to how any hospital hotline work. We call in receptionist and she will redirect us to the right department - just that simple

P/s: The accompany code is included in this PR 😊

Happy coding 😎

Tags

• Facade Pattern
• Golang