title: Facade Pattern for an external API call
body: <p>I am looking at a project that has 3 classes, each with about 15 methods responsible for a variety of operations to get data from an API and return a List, or save data, or some other functionality. One class is a customer class, another is a sales class, etc. </p>
  
  <p>The static methods in all of these classes are a little complex and require some setup that I'd like to streamline. I'd like to start by making things easier for the developers and make a facade that could reduce the complexity and perform some of the initial setup.</p>
  
  <p>In a case where I want to reduce complexity of multiple "service" classes, is it generally acceptable/common to create multiple facades? Or just wrap them into one?</p>
  
  <p>My initial reaction is to make multiple facades since it's more intuitive to the developer, for example "CustomerServiceFacade" or "CustomerService", and then another for SalesService (SalesServiceFacade). Not sure if anyone has recommendations on naming conventions.</p>
  
  <p>Thanks!</p>