title: Azure Service Bus Queues vs Topics for one to many(unique)
body: <p>I have an online service hosted on Azure, that asynchronously sends data to on-premise clients. 
  Each client is identified by an unique code.</p>
  
  <p>Actually there is a single topic, with a subscription for each client which has a filter on the unique code, that is sent as a parameter in the message. No message will ever be broadcasted to all the clients.</p>
  
  <p>I feel that using topic this way is wrong.
  The alternative that comes to my mind is to use a dedicated queue for each client, that is created on first contact</p>
  
  <p>Could this be a better approach?</p>
  
  <p>Thanks</p>