Building Resilient Microservices with Azure Service Bus
Reliable messaging is the backbone of microservices architecture. Azure Service Bus provides enterprise-grade messaging, but using it effectively requires…
12 articles
Reliable messaging is the backbone of microservices architecture. Azure Service Bus provides enterprise-grade messaging, but using it effectively requires…
Service Broker provides queuing and messaging functionality within SQL Server, allowing for decoupled, asynchronous communication between services.
Pipes - a communication channel between two processes. Streams - a data collection that moves from a source to a destination.
Event-driven architecture in 2021 moved from architectural pattern to practical implementation. The tools support it, the patterns are proven, and the…
Queue-triggered Azure Functions are the pattern I recommend most often for decoupling work that doesn't need to happen synchronously. The model is simple…
Use queues to handle variable load: Scale processing with multiple consumers: Process high priority items first: Coordinate long running business processes:…
Event Hubs with Kafka protocol offers: No Kafka cluster management Automatic scaling 99.99% SLA Native Azure integration Pay per throughput pricing Event…
Azure Web PubSub is the lower-level real-time service that sits alongside SignalR. Where SignalR abstracts the transport and provides a hub model for your…
How to use Azure Service Bus sessions, session state, transactions and dead-letter queues with the Azure.Messaging.ServiceBus 7.0 SDK, and when not to bother.
Service Bus is the backbone of reliable, decoupled architectures on Azure.
When to pick Event Grid over Service Bus or Event Hubs, and how to publish, handle, filter and dead-letter events so failed deliveries aren't silently lost.
Why an HTTP call between two services drops work, and how a Service Bus queue with peek-lock, duplicate detection and a watched dead-letter queue fixes it.