What is the facade design pattern?

by

A design pattern is a common way of solving a recurring problem. Classes in all design patterns are just normal classes. What is important is how they are structured and how they work together to solve a given problem in the best possible way.

The Facade design pattern simplifies the interface to a complex system; because it is usually composed of all the classes which make up the subsystems of the complex system.

A Facade shields the user from the complex details of the system and provides them with a simplified view of it which is easy to use. It also decouples the code that uses the system from the details of the subsystems, making it easier to modify the system later.

http://www.dofactory.com/Patterns/PatternFacade.aspx

http://www.blackwasp.co.uk/Facade.aspx

Also, what is important while learning design patterns is to be able to recognize which pattern fits your given problem and then using it appropriately. It is a very common thing to misuse a pattern or trying to fit it to some problem just because you know it. Be aware of those pitfalls while learning\using design patterns.

More Related Contents:

  1. What is dependency injection?
  2. Why is Singleton considered an anti-pattern? [duplicate]
  3. How do the Proxy, Decorator, Adapter, and Bridge Patterns differ?
  4. Factory Pattern. When to use factory methods?
  5. What is a wrapper class?
  6. How will I know when to create an interface?
  7. Why do we need Abstract factory design pattern?
  8. What’s the difference between the Dependency Injection and Service Locator patterns?
  9. Which Typesafe Enum in C++ Are You Using?
  10. Naming Classes – How to avoid calling everything a “Manager”? [closed]
  11. Dependency Injection & Singleton Design pattern
  12. Are utility classes evil? [closed]
  13. Relational Database Design Patterns? [closed]
  14. Is UnitOfWork equals Transaction? Or it is more than that?
  15. How to implement Builder pattern in Kotlin?
  16. Factory, Abstract Factory and Factory Method
  17. Singleton pattern [closed]
  18. Difference between Bridge pattern and Adapter pattern
  19. What is the difference between Builder Design pattern and Factory Design pattern? [closed]
  20. What’s the difference between design patterns and architectural patterns? [closed]
  21. Are there any viable alternatives to the GOF Singleton Pattern?
  22. When should you use the singleton pattern instead of a static class? [closed]
  23. Is global constants an anti-pattern?
  24. REST API Login Pattern
  25. Using a strategy pattern and a command pattern
  26. How do you know when to use design patterns? [closed]
  27. Static factory methods vs Instance (normal) constructors?
  28. What would a Log4Net Wrapper class look like?
  29. When do we need decorator pattern?
  30. Difference betwen Visitor pattern & Double Dispatch

Leave a Comment