Multiple Facade Classes must be combined in 1 Facade Class

Question

Is this some rule that if I have multiple Facade classes they must be combined in 1 Facade Class?

For example, I have a Hospital System with different classes, like Appointment, Patient, Doctor, Medicine.

I created different Facade Classes like, OPD_Facade, Pharmacy_Facade, Visit_Facade, all of them are independent with each other and internally using the other classes and exposing simple methods. My UI (which is client of facade classes) uses appropriate facade to perform different tasks.

Do I need to create 1 central Facade class where these Facade classes must be linking together? Or this whole scheme is NOT actually Facade Pattern? The examples I am seeing on internet usually have 1 central Facade class.

candied_orange · Accepted Answer · 2018-08-17T23:25:24.200

4

The point of any facade is to provide a useful abstraction and interface for the using code. What is behind the facade, multiple functions, multiple objects, or multiple facades is not important. Which is why you have a facade in the first place. To make the complexity of structure go away. Stop focusing on the structure and focus on the way this will be used.

This means the only justification for 1 central facade class would be if there were using code that had a real need to use the whole thing. Without that, unifying everything into one facade is a pointless exercise. It's perfectly fine to use multiple facades when you have multiple uses. Just make something easy for us mere humans to understand.

edited Aug 17 '18 at 23:25

answered Aug 16 '18 at 08:16

candied_orange

102,279
24
197
315

Thanks, I understand and also trying to do the same, the problem is that someone is arguing that the way I am doing is NOT correct way to implement Facade Pattern, that's my question, is my approach OK? – sallushan Aug 16 '18 at 08:28
@sallushan better? – candied_orange Aug 16 '18 at 08:36

Multiple Facade Classes must be combined in 1 Facade Class

1 Answers1