title: Should I change how our microservices communicate?
body: <p>Our application consist of 7 microservices that have some intercommunication. Currently we're using simple storage queues that a microservice publish events to (the number of events is relative low). Then we have a azurefunction for each queue that might call another microservices. This is working fine for us right now the services uses about 20 queues with a corresponding function.</p>
  
  <p>Now we need to handle an blobstorage event, and I did some googling and a started to get really confused. Suddenly there was a lot of questions:</p>
  
  <ul>
  <li>Should we switch to Azure Event Grid
  
  <ul>
  <li>It handles blobstorage without any limitations (functions blobstorage trigger has some)</li>
  <li>It allows for multiple subscribers (storage queues does not)</li>
  <li>It has a lot of fuz - maybe this is the new recommended way</li>
  <li>I like the idea of one central thing, but it reminds me a bit about biztalk...</li>
  </ul></li>
  <li>Should I switch to Azure Service Bus
  
  <ul>
  <li>It has a nice tool (ServiceBusExplorer) for monitoring the queues and listners, and I could to a repost of any failed events </li>
  <li>It visulizes my azure functions subscribers nicely</li>
  </ul></li>
  <li>Should I continue with only storage queues
  
  <ul>
  <li>A bit difficult to monitor, but it works nice</li>
  </ul></li>
  </ul>
  
  <p>I'll be really thankful for any advice or insights to this question.</p>
  
  <p>Thanks</p>