anchor.diff:  need. Technical details that are specific for the service component implementations 
   are handled inside the facade.
   
  -=== Experiences
  +==== Experiences
   
  -Consider the use of a Facade if you must use generic frameworks or systems you cannot modify
  +Consider a Facade if you must use generic frameworks or systems you cannot modify
   e.g. legacy systems.
   
  -=== Applicability
  +==== Applicability
   
   Apply this pattern when clients use a set of components in stereotypcial fashion. 
   Things that can be handled by a facade:
  
positive.code: [[facade]]
  
  === Manage complex client dependencies with a Facade
  
  === Intent
  
  Simplify the interaction of a client with a set of service components. 
  
  === Description 
  
  When clients use a set of components with repeating patterns these
  interaction patterns are implemented in a Facade component.  
  
negative.code: **  error handling
  
  
  ==== Consequences
  
  * Enhances Information Hiding. Clients do not need information about the components' technical detail.
  * Supports DRY principle: complex interactions are implemented in one place. No need to reimplement this in different clients.
  
  ==== Also Known As 
  
  
  ==== Related Patterns 
  
  
  
  