Service Bus allows the messages to be deleted from the Service Bus subscription only after the Subscriber explicitly deletes it from the subscription queue under the peek and lock mode. This shows that having Service Bus between the Event Grid and Subscriber makes the architecture more resilient and fault tolerant. Although we can improve this by using configuration, the problem would not be solved unless a mechanism like Service Bus is in between the Event Grid which will allow the Logic App to work at its own pace. After some initial messages, the Azure Function started failing. We sent 200 messages to the Event Grid Topic separated in 50 seconds with JMeter. The Logic App invoked an Azure Function inside its workflow. In order to validate the above, we created a Topic in the Event Grid and added a Logic App as a Subscriber to test the above.
This may cause the Subscriber to Throttle or become unresponsive. In this article, we will look into the features of both these services and recommend the use of these services as a messaging service between two microservices.Įvent Grid works on a Push mechanism, which means that the Event Grid pushes the event to its Subscribers, whereas in Service Bus, the subscribers pull the messages from the Bus.Īs the Event Grid pushes the messages to the Subscriber, the rate with which the events are pushed to the Subscriber may be more than the rate at which the Subscriber can process the events.
The common candidates of this Azure Messaging service are Azure Event Grid and Azure Service Bus. In the case of Microservices Architecture, one of the common scenarios is to create a Messaging Service between two Microservices.
0 kommentar(er)
