Migrating your messaging workloads to the Cloud with Azure Service Bus
summary
Shows how to move JMS 2.0 messaging workloads (IBM MQ, TIBCO EMS, JBoss A‑MQ) to Azure Service Bus by swapping providers and changing the connection string in a Spring application so existing JMS code and tools keep working. Covers Service Bus queues, topics, subscriptions, filtering/routing, and JMS 2.0 compatibility across Basic/Standard/Premium tiers (Premium adds sessions, higher throughput and advanced features), demonstrates end-to-end message flow including multi-megabyte messages, and shows integration with Logic Apps, Functions and private networking.
AI-written summary · about
chapters (20)
- 0:00Cloud messaging
- 1:48Azure Service Bus choice
- 3:56Service Bus tiers
- 6:24Service Bus reliability
- 8:08Enterprise integration
- 10:14Cross-platform support
- 12:43Cost comparison
- 15:07Migrating workloads
- 17:34Demo setup
- 21:49Sending messages
- 24:00Service Bus with Artemis
- 27:20Message filtering
- 30:36Subscriptions and visibility
- 33:51Deferred messages
- 36:18Dead-letter queues
- 38:10Large messages
- 41:00Demo recap
- 44:31Security and compliance
- 46:16Performance benefits
- 48:02Q&A
related talks
33mConnecting clients with Windows Azure Service Bus
24mMigration from On-Prem Messaging System to The Cloud
45mThe latest and greatest from Azure Service Bus
01mGA - Introduction
59mBuilding Resilient Applications In Microsoft Azure
48mA Beginner's Guide to Inter-Service Messaging
53mMaking tomorrow's code look like today's
56mLittle Fluffy Clouds