title: How to prevent changing client code for achieving Azure SQL Server Sharding?
body: <p>I'm just wondering if there is a solution for implementing Azure Sql Server sharding in a way you don't have to change the client code. I found articles about the implementation but in all of them you need to create an extra abstraction and you need to store all the information about all of the shards.</p>
  
  <p>For example for MongoDB you can solve this by introducing a load balancer and then the load balancer will redirect the client to the appropriate Shard.</p>
  
  <p>Is that possible with Sql Server?</p>