You are developing a solution that will use Azure messaging services.
You need to ensure that the solution uses a publish-subscribe model and eliminates the need for constant polling.
What are two possible ways to achieve the goal? Each correct answer presents a complete solution.
NOTE: Each correct selection is worth one point.
Click on the arrows to vote for the correct answer
A. B. C. D.AC.
It is strongly recommended to use available messaging products and services that support a publish-subscribe model, rather than building your own.
In Azure, consider using Service Bus or Event Grid.
Other technologies that can be used for pub/sub messaging include Redis, RabbitMQ, and Apache Kafka.
https://docs.microsoft.com/en-us/azure/architecture/patterns/publisher-subscriberTo achieve the goal of using a publish-subscribe model and eliminating the need for constant polling in a solution that uses Azure messaging services, there are two possible ways to achieve it:
Azure Service Bus is a messaging service in Azure that supports messaging between applications and services. It provides a publish-subscribe model that allows multiple subscribers to receive messages from a single topic, without the need for constant polling.
Service Bus uses a topic-subscription model, where messages are sent to a topic and subscribers receive messages from a subscription. Subscribers can register to receive messages from a specific subscription, or use filters to receive messages that match specific criteria.
Service Bus also provides a feature called "Auto Forwarding" which enables you to forward messages automatically from one queue or topic to another, allowing you to chain together multiple topics or queues to create complex messaging scenarios.
Azure Event Grid is a fully managed event routing service that enables you to create event-driven architectures. It provides a publish-subscribe model that allows multiple subscribers to receive events from a single publisher, without the need for constant polling.
Event Grid uses a publisher-subscriber model, where events are published to a topic and subscribers receive events from a subscription. Subscribers can register to receive events from a specific subscription, or use filters to receive events that match specific criteria.
Event Grid also provides built-in support for many Azure services, including Azure Blob Storage, Azure Resource Manager, and Azure Event Hubs, which makes it easy to create event-driven solutions that span multiple Azure services.
Therefore, both Azure Service Bus and Azure Event Grid are viable options to achieve the goal of using a publish-subscribe model and eliminating the need for constant polling in a solution that uses Azure messaging services.