Middleware Showdown: Exploring Diverse Messaging Solutions
summary
Compares concrete middleware choices: Amazon SQS (cheap, per-account queues, FIFO groups and delayed delivery), RabbitMQ (RabbitMQ exchanges and bindings for fast fan-out and Quorum queues, easy Docker/cloud deploy), Azure Service Bus (session ordering, premium tier ~ $600/mo, topic→subscription cost overhead), Apache Kafka (Kafka 50,000 msgs/partition/s for durable event streams and long retention), and using SQL as a queue (MassTransit SQL transport shows hundreds/sec on SQL Server, thousands/sec on Postgres) and when each actually fits.
AI-written summary · about
chapters (16)
- 0:00Welcome
- 1:56Messaging in modern apps
- 6:10Middleware and message types
- 9:01Queues vs streams
- 12:53Amazon SQS deep dive
- 16:45RabbitMQ features
- 19:55Azure Service Bus
- 23:01Polymorphic messaging with MassTransit
- 27:36ActiveMQ and Amazon MQ
- 29:03SQL transport with MassTransit
- 32:13Outbox pattern hybrid
- 34:17Streams and Apache Kafka
- 38:15Kafka use cases
- 41:07Azure Event Hubs vs Kafka
- 45:03Actor model vs messaging
- 48:37Q&A
related talks
01h 03mChoosing the Right Messaging Solution for Your Architecture
01h 16mChoosing the Right Messaging Solution for Your Architecture
41mForget about HTTP
46mReal-world Examples of Message Queue Usage: Insights from RabbitMQ
42mIt's like 10,000 streams when what you need is a queue
30mApplication integration patterns for microservices
53mAzure Messaging, Queueing, and Events - Which service is right for your solution?
55mImplementing scalable messaging patterns in Azure