title: Azure Service Bus Topic Architecture
body: <p>I've been working through the <a href="https://github.com/dotnet-architecture/eShopOnContainers" rel="nofollow noreferrer">eShopOnContainers</a> project provided by Microsoft, honing my microservice skills in general. One of the big concepts is the introduction of an Event Bus. I've opted to try it with Azure Service Bus but my experience with the platform is limited.</p>
  
  <p>I've managed to get the project running after manually creating the Topics, Subscriptions, etc, but this raises a few questions:</p>
  
  <p>Is it not the responsibility of the subscribing application to create it's own Subscription in Azure? e.g. on startup?</p>
  
  <p>Conceptually, Topics represent different event stacks, correct? E.g. Customers, Ordering, etc? Or are they intended to be domain event boundaries? E.g. in this application, 'eShop' would be the topic.</p>
  
  <p>Azure deployments is a whole other topic, but related to the Service Bus configuration, are there any recommended techniques for managing that within source control?</p>
  
  <p>Any insight is greatly appreciated.</p>