The use of Facade Design Pattern (Before-After)

  • Facade is a structural design pattern.
  • There is’nt  hard coupling between facade and sub-systems (loose coupling)
  • Sub-systems can work alone
  • Facade class use subsystem
  • Facade use for simplicity access to functionality in complex designed subsystems
  • Facade providers customized high-level interface

Before using facade design

facade-before

After using facade design

facade-after

Another facade design to reduce the complexity and dependency

facade-another

About these ads

2 thoughts on “The use of Facade Design Pattern (Before-After)

  1. The view above is very high level. Firstly, you may develop a facade class for your each subsystem to reduce the complexity and dependency. Facade manages the classes in the subsystem and provide required services to the external world. So, class level usage of the facade pattern is very common. And also, using facade (when you are decomposing your systems into subsystems) in your software architecture is very good practice.
    Thanks for focusing on these issues.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Connecting to %s