What should you recommend?

You are designing an Azure application. The application includes services hosted in different
geographic locations. The service locations may change.
You must minimize the cost of communication between services.
You need to recommend an approach for data transmission between your application and Azure
services. The solution must minimize administrative effort.
What should you recommend?

You are designing an Azure application. The application includes services hosted in different
geographic locations. The service locations may change.
You must minimize the cost of communication between services.
You need to recommend an approach for data transmission between your application and Azure
services. The solution must minimize administrative effort.
What should you recommend?

A.
Azure Table storage

B.
Service Bus

C.
Service Management API

D.
Azure Queue storage

Explanation:
The cost of ACS transactions is insignificant when performing messaging operations against Service
Bus queues. Service Bus acquires one ACS token per a single instance of the messaging factory
object. The token is then reused until it expires, after about 20 minutes. Therefore, the volume of
messaging operations in Service Bus is not directly proportional to the amount of ACS transactions
required to support these operations.

Azure Queues and Service Bus Queues – Compared and Contrasted
https://msdn.microsoft.com/library/azure/hh767287.aspx

Show Hint

Leave a Reply 4

Your email address will not be published. Required fields are marked *

Tommy

Tommy

I think it should be either C or D ?

Reply

Bartolillo

Bartolillo

Correct answer is B

https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-azure-and-service-bus-queues-compared-contrasted

Reply

Joni

Joni

I think [D] – Azure queue storage are the recommendation for messaging “within and between services”. They are simple to administer compare to service bus queues which “are part of a broader Azure messaging infrastructure that supports queuing as well as publish/subscribe, and more advanced integration patterns.”

https://docs.microsoft.com/en-us/azure/service-bus-messaging/service-bus-azure-and-service-bus-queues-compared-contrasted

Storage queues, which are part of the Azure storage infrastructure, feature a simple REST-based Get/Put/Peek interface, providing reliable, persistent messaging within and between services.

Service Bus queues are part of a broader Azure messaging infrastructure that supports queuing as well as publish/subscribe, and more advanced integration patterns. For more information about Service Bus queues/topics/subscriptions, see the overview of Service Bus.

Reply