Design Pattern - Facade

Question

The Facade design pattern is centered around "Association" over inheritance, correct?

If there is a car system like this:

Car (class)

-> Body (class)

-> Steer wheel (class)

-> Chassie (class)

-> Wheels (class)

Then these classes are not inherited from Car are they? Because in theory, I've been taught that inheritance has a "Can be" relationship.. "Person CAN BE a Student" ... "Car HAS A Chassie" Which would infer that it is Association?

Any ideas? :)

I'm not sure what "facada" is, but that looks like composition to me. — Waleed Khan, Oct 29 '12 at 17:21
you could check this question asked about Facade [What is facade design pattern?](http://stackoverflow.com/questions/5242429/what-is-facade-design-pattern) — Akram Berkawy, Oct 29 '12 at 17:39

score 1 · Answer 1 · answered Oct 29 '12 at 17:32

Yes. That is correct. Facade is centered around Association. It wraps a variety of related subsystems (which mostly work together) to provide a meaningful and simple interface to the client. The subsystems need not be in the same inheritance hierarchy but are almost always associated.

Your car example :

http://www.go4expert.com/forums/showthread.php?t=5127#facade

score 1 · Answer 2 · answered Oct 29 '12 at 17:48

I would agree with you. The idea of the facade pattern is that you have bunch of associated objects that you wrap in a facade to make managing and manipulating those objects easier.

As Waleed Khan said in the comments, this example kind of blurs the line with composition because car is made of the different parts. We may have a case where the objects that make up the facade all work together without directly being the pieces of some larger entity.

The car example makes things easy because we can do things like car.turnLeft() which may affect both the wheels and the steering wheel. The coordination between the objects is handled by Car.

So I could have that has a function called "compare" and that's all the user see's, it's all that persons aware of. Behind the scenes, it actually works by doing Correlation to find the similarities of the two values.. This would be a Facade? — Phorce, Oct 29 '12 at 17:50

score 1 · Answer 3 · answered Oct 29 '12 at 18:29

I would NOT agree with you, facade is not centered around association neither inheritance.

A facade is an object that provides a simplified interface to a larger body of code

meaning that it is used to provide higher-level view of subsystems and hide its complexity, whatever was the implementation of the subsystems is based on, association or inheritance.

another alternative to facade is transparent facade which let the client being able to go through it, and get access to individual operations of the sub systems.

the car system you are asking about is just an example, the pattern is not limited to it.

One upvote for mentioning the simplified interface to a larget body of code.In android also they use Facade design pattern for context instance which gives access to the environment variables(app state,current activity,android system) — Durai Amuthan.H, May 31 '14 at 15:36

score 0 · Accepted Answer · answered Oct 29 '12 at 18:45

I agree with the sentiment that whether the objects underneath are associated or inherit is an implementation detail which doesn't have much to do with how the pattern functions.

Frankly, Facade is a pattern that attempts to accomplish the same thing that componentization does: you cannot always make it easy to manipulate a bunch of different things, but you need one interface. The most common example you see all the time of Facade being applied in the Java world is to provide a means of using the JavaMail interface. You don't want to even have to deal with Sessions. It's stupid. Likewise, Spring's persistence classes are a facade, though they allow you to ignore sessions by using Aspects, and they also introduce perils of simplification, in that the session is actually different in successive invocations, hence OpenSessionInView.

The key question to ask in wondering whether Facade applies is what are you going to be able to hide? And will you really be able to accomplish it?

score -2 · Answer 5 · answered Oct 29 '12 at 17:31

-2

The Facade pattern is a variant of the Adapter pattern. The Adapter pattern "wraps" an interface and converts it to another (adapting it to the form in which a client expects it). Often used to adapt a new interface to older client software. Or to wrap old, crufty, Big-Ball-O-Mud software with a shiny new, presumably cleaner interface, with an eye towards replacing the old crufty code later.

The Facade pattern, on the other hand, wraps an interface, presenting a simplified form of it to the client.

Neither has much to do with composition versus inheritance.

You want look up the book Head First Design Patterns, by Eric Freeman and Elizabeth Freeman. Far better than the GO4 book, IMHO, as far as learning to do something with design patterns.

Head First Design Patterns Cover

answered Oct 29 '12 at 17:31

Nicholas Carey

71,308
16
93
135

It's really not a variant. They are both Structural patterns, but they are VERY different. – Rob Oct 29 '12 at 18:40
1

The idea that that book is better than the Gang of Four is patently absurd. – Rob Oct 29 '12 at 18:46
Go4 good for talking about patterns from the standpoint of theory. Next to useless for explaining how to **apply** them in a practical way. – Nicholas Carey Oct 29 '12 at 19:21
So says you. It was voted the most important book of the last decade in Dr. Dobbs in 2000. Most people agree it's the most important of the last 2. I find their explanations fine, and don't even mind that the examples are in C++ and sometimes Smalltalk. One of the best books ever written, period. – Rob Oct 29 '12 at 19:23
This brain friendly guide, on the other hand, is like reading a cartoon version of Faulkner. I have this book and have looked at it plenty of times. I would not recommend it to anyone. – Rob Oct 29 '12 at 19:24

Design Pattern - Facade

5 Answers5