As an IT service provider in the field of cloud application integration, it’s our pleasure to support you to bring your cloud applications and services into interaction.
Microsoft Azure offers Service Bus which is a cloud messaging service and Azure Services (Web role and Worker role) as a comprehensive mode of communication. By using Microsoft Azure Services and Microsoft Azure Service Bus, we can interact with your cloud applications and services with your on-premise applications and on-premise services in various forms.
Microsoft Azure Service Bus offers several techniques:
- Queues/ Queues: Queues are available for one-way communication. The sent messages are cached until they are received. Each message is received by a single recipient. A queue plays a role in Brocker. The waiting queues support the FIFO (first-in-first-out) principle.
- Topics: A topic plays the role of Brocker with several subscriptions for one-way communication. Each subscription can use filters to receive only messages that are requested.
- Relays: Relays are for two-way communication. Unlike queues and topics, a relay does not store sent messages—it’s not a broker. Instead, it forwards them to a target application.
A solution to a hybrid scenario using queues must take into consideration in addition to other criteria:
- The solution is designed to support automatic duplicate detection and to guarantee “at-most-once” delivery.
- Message size cannot exceed the allowed message size of waiting queues.
- The solution regards the data volume in terms of queue size.
- The solution should respect the Time To Live (TTL) / validity period. TTL is the maximum duration during which the message can be received.
Azure Services Chart:
For any questions, comments, or concerns? Please contact us.