Choosing the Right Messaging Solution for Your Architecture
summary
Compares AWS SQS, RabbitMQ, and Azure Service Bus with code samples in a GitHub repo and concrete limits: SQS gives 1 MB messages, up to 120,000 in‑flight messages, standard queues are at‑least‑once with DLQ only via max receive count and SNS for pub/sub; Azure Service Bus shows standard 256 KB / premium 100 MB, ~5 GB queue (partitioning to 80 GB), native pub/sub with SQL/correlation filters, auto DLQs, sessions and transactions; RabbitMQ is self‑hosted, AMQP/MQTT, plugins for delayed messages, quorum queues use Raft and handle poison messages.
AI-written summary · about
chapters (6)
- 0:00Messaging solutions intro
- 1:28Amazon SQS overview
- 25:00Azure Service Bus use cases
- 45:51RabbitMQ strengths
- 1:04:32Choosing the right broker
- 1:07:42Q&A vendor lock-in
related talks
01h 03mChoosing the Right Messaging Solution for Your Architecture
50mMiddleware Showdown: Exploring Diverse Messaging Solutions
53mAzure Messaging, Queueing, and Events - Which service is right for your solution?
01h 01mBeyond Pub/Sub - Advanced Messaging Patterns
45mThe latest and greatest from Azure Service Bus
32mRabbitMQ in Real Life - Tips and Tricks
01h 00mRabbit MQ vs Kafka: When, Which, Where?
40mPerformance Improvements