anchor.diff:  **  error handling
   
   
  -=== Consequences
  +==== 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 
  +==== Also Known As 
   
   
  -=== Related Patterns 
  +==== Related Patterns 
   
   
   
  
positive.code: need. Technical details that are specific for the service component implementations 
  are handled inside the facade.
  
  === Experiences
  
  Consider the use of a Facade if you must use generic frameworks or systems you cannot modify
  e.g. legacy systems.
  
  === Applicability
  
  Apply this pattern when clients use a set of components in stereotypcial fashion. 
  Things that can be handled by a facade:
  
negative.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.  
  