I've been a zone leader with DZone since 2008, and I'm crazy about community. Every day I get to work with the best that JavaScript, HTML5, Android and iOS has to offer, creating apps that truly make at difference, as principal front-end architect at Avego. James is a DZone Zone Leader and has posted 639 posts at DZone. You can read more from them at their website. View Full User Profile

Design Patterns Uncovered: The Facade Pattern

  • submit to reddit

This article will focus on the Facade pattern. So far in our design patterns we've already looked at the Observer and Adapter patterns. Facade has some similarities with the Adapter, so it's a logical next step in our series. 

Facades in the Real World 

Facades are all around us in the real world.  Operating systems are one such example - you don't see all the inner workings of your computer, but the OS provides a simplified interface to use the machine. Buildings also have a facade - the exterior of the building. Wikipedia gives us a nice link between software architecture and standard architecture: 

In architecture, the facade of a building is often the most important from a design standpoint, as it sets the tone for the rest of the building

So, in a nutshell, a Facade aims to make things look cleaner and more appealling.

Design Patterns Refcard
For a great overview of the most popular design patterns, DZone's Design Patterns Refcard is the best place to start. 

The Facade Pattern

Like the Adapter pattern, Facade is known as a structural pattern, as it's used to identifying a simple way to realize relationships between entities. The definition of Facade provided in the original Gang of Four book on Design Patterns states: 

Provide a unified interface to a set of interfaces in a subsystem. Façade defines a higher-level interface that makes the subsystem easier to use.

The diagram definition of the Facade pattern is quite simple - all you're really doing is insulating client from the subsystem:


Like the adapter pattern, the Facade can be used to hide the inner workings of a third party library, or some legacy code.  All that the client needs to do is interact with the Facade, and not the subsystem that it is encompassing.

The following sequence diagram illustrates how the pattern is used by a client: 


Where Would I Use This Pattern?

As the concept behind facade is to simplify an interface, service oriented architectures make use of the facade pattern. For example, in web services, one web service might provide access to a number of smaller services that have been hidden from the caller by the facade. Similarly, a typical pattern in OSGi bundles is to provide an interface package that is exposed to users of the bundle. All other packages are hidden from the user.

So How Does It Work In Java?

Let's put together a simple example in Java code to illustrate the pattern. Let's take a travel agent site for example, that allows you to book hotels and flights. We have a HotelBooker:

public class HotelBooker

public ArrayList<Hotel> getHotelNamesFor(Date from, Date to)
//returns hotels available in the particular date range



And a FlightBooker:

public class FlightBooker

public ArrayList<Flight> getFlightsFor(Date from, Date to)
//returns flights available in the particular date range



Both of these have Hotel and Flight datatypes, which the client has knowledge about. They could be provided in the same package as the Facade for example. 

The TravelFacade class allows the user to get their Hotel and Flight information in one call:


public class TravelFacade

private HotelBooker hotelBooker;
private FlightBooker flightBooker;

public void getFlightsAndHotels(Date from, Data to)
ArrayList<Flight> flights = flightBooker.getFlightsFor(from, to);
ArrayList<Hotel> hotels = hotelBooker.getHotelsFor(from, to);

//process and return



All that the client needs to worry about is the Facade class: 

public class Client

public static void main(String[] args)
TravelFacade facade = new TravelFacade();
facade.getFlightsAndHotels(from, to);

As you can see, it's just a simple approach to encapsulating data.

Watch Out for the Downsides

By introducing the Facade into your code, you will be hardwiring subsystems into the Facade. This is fine if the subsystem never changes, but if it does, your Facade could be broken. Therefore, developers working on the subsystem should be made aware of any Facade around their code.

Other Articles in This Series
The Observer Pattern
The Adapter Pattern
The Facade Pattern
The Factory Method Pattern
The Abstract Factory Pattern
The Singleton Pattern
The Strategy Pattern
The Visitor Pattern

Next Up

 We'll get to the Singleton pattern next week.



Mateusz Mrozewski replied on Sat, 2010/02/13 - 5:23am

In the second listing the class name should be FlightBooker.

 Thank you for the series, it's excellent. It will be very valuable for anyone who wants to learn design patterns. Keep going :)

Vedhas Pitkar replied on Sun, 2010/02/14 - 11:54pm

Indeed, very nice series!! I like your "in the Real World " part more as it helps one to visualize the design pattern. Awaiting the next one.. PS: I would be nice if you would also explain the subtle differences between 2 similar patterns i.e. Adapter & Facade, Strategy & template etc...

James Sugrue replied on Mon, 2010/02/15 - 2:46am in response to: Vedhas Pitkar

Thanks for the comments. I'll make sure to add in the differences in the future patterns, and will edit the existing articles in the series soon to illustrate the differences.


Sriram Varadharajan replied on Mon, 2010/02/15 - 8:48am

excellent work . looking forward to singleton pattern discussion .

Bogdan Marian replied on Mon, 2010/02/15 - 9:06am

I really appreciate your effort  you put in describing the GOF design patterns.

I can hardly wait for the next articles.

Well done, James.

prashant jalasutram replied on Tue, 2010/02/16 - 5:53am

nice post sir. Keep writing about all patterns. Thanks Prashant Jalasutram http://prasanthaboutjava.blogspot.com/

Mladen Girazovski replied on Tue, 2010/02/16 - 2:38pm in response to: Sriram Varadharajan

looking forward to singleton pattern discussion . 

 You're kidding, right?

Sudhakar Ramasamy replied on Wed, 2010/03/17 - 10:48pm

The TravelFacade.getFlightsAndHotels(Date from, Date to) should return an object, correct?

JavaOnZone Neon replied on Thu, 2011/07/21 - 2:40pm

Like it. It's easy to understand with these simple examples.

nilesh gule replied on Mon, 2012/07/16 - 9:59am

Nicely depicted using hotels and flights. This is one of the best example I have seen for Facade pattern. I recently posted about C# implementation of Facade using Home Loan as an example. 


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.