Clemens Vasters explains the differences and use cases for Azure's messaging services, including Service Bus, Event Grid, and Event Hubs.
Azure Messaging services, including Azure Service Bus, Azure Event Grid, Azure Event Hubs, Azure Relay, Azure Stream Analytics, and Fabric Event Streams, offer a suite of tools for reliable message delivery and event-driven architecture. This session will provide a clear understanding of each service’s capabilities and how they can be integrated to build scalable, resilient applications.
We’ll discuss the selection process for the right messaging tool based on your application’s needs, supported by real-world examples. The focus will be on practical guidance and best practices for implementing a cohesive messaging strategy on Azure, and we will look at the latest news from each product.
Join us to learn how Azure’s messaging services can streamline your application’s communication layer, fostering efficiency and innovation in your cloud-based solutions.
Why it's here
1 person recommends this
What people say. Recommended as an excellent architectural guide to choosing the right messaging and event-driven patterns.
b
u/broken-neuronsin r/dotnet • Recommends
On “Forwarding ≈30k events/sec from Kafka to API consumers”
…ience if one of the subscribers isn’t available
- do you have any SLA’s to maintain
- is only push on the table, or can clients pull instead.
Webhooks are rarely a good architectural decision.
- https://news.ycombinator.com/item?id=42309742
- https://blog.sequinstream.com/events-not-webhooks/
I also recommend this talk from Clemens Vasters: link to this video…