title: WCF service access for redunancy (failover)
body: <p>I'm looking for the correct way to have redundancy for a WCF service. I think I'm trying to solve a "infrastructure" issue in code. I'm not up to speed on load balancers but it seems like there should be something like routers to exactly this.</p>
  
  <pre><code>// Cycle through the list of service.
  foreach (var uri in InfrastructureInformation.ServiceUris)
  {
      try
      {
          using (var client = WcfClientFactory.Create&lt;ServiceClient&gt;(uri))
          {
              // Do stuff here.
          }
      }
      catch
      {
          // todo: Do not catch "exception" here. We have to find a better way of doing this.
          // Try the next URI.
      }
  }
  </code></pre>
  
  <p>Seems like there should be a way to have one URI that I could hit that some "balancer" would hand off to an available service. If one service goes down for maintenance then the balancer would just not give any request to that service. </p>
  
  <p>Now I know about WCF routing and I thought well that's the answer. Just put up a WCF router and have it hand out the connection but what happens if it falls over? Doesn't this give you a single point of failure? I'm looking for something more industrial.</p>