Connecting clients with Windows Azure Service Bus
summary
Slides and demos show how Windows Azure Service Bus actually behaves: queues with FIFO guaranteed delivery, topics for pub/sub and filters, relays for on‑premise firewalled endpoints and notification hubs for cross‑platform mobile push. Demonstrations use PHP REST calls, a Java/Tomcat VM and WebMatrix‑hosted pages; authentication uses SAS tokens and connection strings with per‑key access policies. Measured numbers: about 2,000 messages/sec with ~100 ms latency, default message size 64 KB, and billing per service call (watch for empty polls).
AI-written summary · about
chapters (4)
- 0:00Start
- 5:52Benefits Guaranteed delivery Loosely coupled Interoperability Low cost maintenance
- 7:35Various Models Queues Topics
- 29:03Average latency 100 ms
related talks
50mMigrating your messaging workloads to the Cloud with Azure Service Bus
45mThe latest and greatest from Azure Service Bus
59mBuilding Resilient Applications In Microsoft Azure
01h 00mBuilding Resilient Applications In Microsoft Azure
56mLittle Fluffy Clouds
01mGA - Introduction
51mBuilding for Resiliency and Scale in the Cloud
01h 02mBuilding cloud-ready applications in .NET