title: Choosing between .NET Service Bus Queues vs Azure Queue Service
body: <p>Just a quick question regarding an Azure application. If I have a number of Web and Worker roles that need to communicate, documentation says to use the Azure Queue Service. </p>
  
  <p>However, I've just read that the new .NET Service Bus now also offers queues. These look to be more powerful as they appear to offer a much more detailed API. Whilst the .NSB looks more interesting it has a couple of issues that make me wary of using it in distributed application. (for example, Queue Expiration... if I cannot guarantee that a queue will be renewed on time I may lose it all!).</p>
  
  <p>Has anyone had any experience using either of these two technologies and could give any advice on when to choose one over the other.</p>
  
  <p>I suspect that whilst the service bus looks more powerful, as my use case is really just enabling Web/Worker roles to communicate between each other, that the Azure Queue Service is what I'm after. But I'm just really looking for confirmation of that before progamming myself in to a corner :-)</p>
  
  <p>Thanks in advance.</p>
  
  <h1> UPDATE </h1>
  
  <p>Have read up about the two systems over the break. It defo looks like .NET service bus is more specifically designed for integrating systems rather than providing a general purpose reliable messaging system. Azure Queues are distributed and so reliable and scalable in a way that .NSB queues are not and so more suitable for code hosted within Azure itself.</p>
  
  <p>Thanks for the responses.</p>