62 votes
MSMQ Azure
Azure Queues are nice, but having a transactional and durable queues with guaranteed only-once delivery would be a big helper. Loosing inherent scalability is OK (just like it works out with the SQL Azure).
Suggestion in detail is here: http://abdullin.com/journal/2010/5/21/windows-azure-most-wanted-msmq-azure.html
Tom van Oost
Very important for existing applications (using MSMQ) that want to migrate to Azure.
Ruppert Koch
The September '11 release of Azure AppFabric Service Bus provides exactly what you are looking for: Transactional queues and topics/subscriptions with exactly-once delivery guarantees, deadlettering, scheduled messages, etc.
Jonathan
A reliable, reasonably-scaled de-duplicating queue is a requirement for our application.
Jonathan
A reliable, reasonably-scaled de-duplicating queue is a requirement for our application.
Jonathan
A reliable, reasonably-scaled de-duplicating queue is a requirement for our application.
Yoel Arnon
That would require MS to change of the MSMQ storage model - which is based on local memory-mapped files - but I agree it worth the effort. It would allow many existing MSMQ based LOB applications to have a smooth transition to Azure, and a better communication model between on premise and Azure apps.
Good to know MSMQ is still so relevant, almost 16 years since I started working on it in the Microsoft "Falcon" (MSMQ) development team.
Yoel - www.msmq.biz
seankearon
This makes a lot of sense for porting a whole load of MSMQ code out there to the cloud.