title: Are there disadvantages of using large number of entities in Azure ServiceBus
body: <p>In another words, if I create messaging layout which uses rather large number of messaging entities (like several thousands), instead of smaller number, is there something in Azure ServiceBus that gets irritated by that and makes it perform less than ideally, or generates significantly different costs. Let us assume that number of messages will remain roughly the same in both scenarios.</p>
  
  <p>So to make clear I am not asking if messaging layout with many entities is sound from applications point of view, but rather is there in Azure some that performs badly in such situations. If there are advantages to it (perhaps Azure can scale it more easily), that would be also interesting.</p>
  
  <p>I am aware of 10000 entites limit in single ServiceBus namespace.</p>