But, I just read that the new .NET Service Bus now also provides queues. These look more powerful because they seem to provide a more detailed API. Although the .NSB looks more interesting, there are a few questions that make me Be cautious when using it in distributed applications. (For example, Queue Expiration…If I can’t guarantee that the queue will be updated on time, I might lose everything!).
Does anyone have any experience using it? Either of these two technologies, and can give any suggestions on when to choose one.
I suspect that although the service bus looks more powerful, my use case is actually just to make the Web / Worker roles can communicate with each other, Azure Queue Service is what I am after. But I really confirm this before looking for confirmation, and then code myself into the corner:-)
Thanks in advance.
UPDATE
I have read about the two systems of rest time. It looks like .NET Service Bus is more dedicated to integrated systems rather than providing general reliable messaging systems. Azure queues are distributed It is reliable and scalable. Among them, the .NSB queue is not, so it is more suitable for the code hosted by Azure itself.
Thank you for your reply.
Just a quick question about Azure applications. If I have many Web and Worker roles that need to communicate, the document says to use Azure Queue Service.
However, I just read that the new .NET Service Bus now also provides queues. These look more powerful because they seem to provide a more detailed API. Although the .NSB looks more interesting, there are a few issues that keep me in the distributed Be cautious when using it in applications. (For example, Que ue Expiration …If I cannot guarantee that the queue will be updated on time, I may lose everything! ).
Does anyone have any experience using any of these two technologies, and can give any suggestions on when to choose a technology.
I doubt though The service bus looks more powerful, but my use case is actually just to allow Web/Worker roles to communicate with each other, Azure Queue Service is what I am after. But I really confirm this before looking for confirmation, and then code myself into the corner 🙂
Thanks in advance.
UPDATE
I have read about the two systems of rest time. It looks like the .NET service bus is more specialized It is an integrated system rather than providing a general reliable messaging system. Azure queues are distributed, so reliable and scalable. Among them, NSB queues are not, so it is more suitable for the code hosted by Azure itself.
Thank you Reply.
I recommend that you stick to Azure Queues for communication between web and worker roles. Using queues is an official and sanction for communication between Azure processes Way, I sincerely doubt that you program yourself to a corner. Service Bus (AppFabric) has a higher overhead, and although it is very suitable for communicating with external applications, it may not be the best choice for fast and simple messages in Azure applications .