title: Azure service bus: is it wise to create a separate topic for every event you broadcast?
body: <p>I am trying to design the strategy that my organization will employ to create topics, and which messages will go to which one. I am looking at either creating a separate topic for each event, or a single topic to hold messages from all events, and then to triage with filters.  I am convinced that using a separate topic for every event is better because:</p>
  
  <ul>
  <li>Filters will be less complex and thus more performant, since each
  event is already separated in its own topic.</li>
  <li>There will be less chance of message congestion in any given topic.</li>
  <li>Messages are less likely to be needlessly copied into any given
  subscription.</li>
  <li>More topics means more messaging stores, which means better message
  retrieval and sending.</li>
  <li>From a risk management perspective, it seems like having more topics
  is better.  If I only used a single topic, an outage would affect all
  subscribers for all messages.  If I use many topics, then perhaps outages would only affect some
  topics and leave the others operational.</li>
  <li>I get 12 more shared access keys per topic.  It's easier to have more granular control over which topics are
  exposed to which client apps since I can add/revoke access by
  add/revoking the shared access key for each app on a per-topic basis.</li>
  </ul>
  
  <p>Any thoughts would be appreciated</p>