title: What is better single or multiple routes for REST service?
body: <p>I have multi-tenant SaaS application and on startup I setup routes like this:</p>
  
  <pre><code>https://my.com/customer1/mobile 
  https://my.com/customer1/integration
  https://my.com/customer2/mobile 
  https://my.com/customer2/integration
  https://my.com/customer3/mobile 
  https://my.com/customer3/integration
  https://my.com/customer4/mobile 
  https://my.com/customer4/integration
  </code></pre>
  
  <p>When I add new customer I have to recycle pool so routes rebuild. I'm not sure if that's the best approach for what I'm doing...</p>
  
  <p>I can create just 2 routes </p>
  
  <pre><code>https://my.com/mobile 
  https://my.com/integration
  </code></pre>
  
  <p>And then pass AccountId in HTTP header along with my auth information. Would it be cleaner? What do you think about performance, having less routes should be benefitial, correct?</p>