Posted inService Bus
Microsoft
9 years ago
BrokeredMessage.Defer(); should send a message to the back of the line
I use the Azure Service Bus in a geographically distributed environment. I also process messages in vertically and horizontally scaled out services.Very often I will receive a message from the service bus for processing, but don't have enough information to complete the processing, (most of the time this is because I am waiting for SQL replication across continents) so I'll have to try again later.Seems like a job for BrokeredMessage.Defer()! But alas, that causes the message to immediately get returned when I call Client.Receive(); even if there are thousands of messages in the queue / subscription that I have not even touched yet. So I end up pulling down the same message(s) rapidly and hitting the SQL server trying to lookup information that isn't there yet, while there are messages in my queue that I could potentially have enough information available to complete their processing.The way I have gotten around this, is to let the brokeredMessage simply time out. But this is a terrible approach.What would be nice, is if the BrokeredMessage.Defer(); call would send the message to the back of the bus so to speak, so that messages that I have not tried processing yet can get a chance before I try that particular message again.Another useful idea would be to add an overload to BrokeredMessage.Defer(); that accepts a TimeSpan. That way I can tell the service bus don't redeliver this message until that time period has passed
Planned
All IdeasPlanned
Company Response
Eldert Grootenboer
Company Response
11 months agoVote
4 Comments