azureservicebus - How Reliable is access to Azure Service Bus? -
i have azure vm running third party server process. server process notifies me of important events calling executable give it, passing in data command line argument.
this data needs queued , processed worker.
it's important these notifications aren't missed, i'm wondering:
is acceptable (given requirement) queue messages directly azure service bus?
or should queue first local msmq, have worker reads messages msmq , pushes them azure service bus?
thanks
the access service bus reliable, have build solution in order cope "transient faults". way can check if fault happens (a temporary 404 on queue, connection problem @ side, etc). these faults called transient faults , should retry on them. this, service bus client has built in functionality , on client, can specify retrypolicy. there different retry policies available , can create own (exponentialbackoff, etc) check : http://msdn.microsoft.com/en-us/library/windowsazure/microsoft.servicebus.messaging.messagecliententity.retrypolicy.aspx
if need client application capable of working offline, might have build in custom store-forward capabilities (you mentioned msmq, can use service bus windows server). downside there no out of box store-and-forward capabilities @ moment.
hope helps
Comments
Post a Comment