Building a scalable multichannel notification system
summary
Vonage builds a RabbitMQ-backed multichannel notification bus that routes messages by namespace+application tuples, implements a Shredder sharding service to allocate shards, and moves from federation and headers exchanges to a single-cluster, direct exchange design for performance. Management plugin memory leaks lead to a lightweight sidecar for user auth and use of rabbitmqctl for metrics. Mobile push is handled by a push-me service with muting and event versioning to satisfy iOS 13 rules. Load testing uses Locust, scaling tests up to millions of simulated users.
AI-written summary · about
chapters (8)
- 0:0002:25 - Introduction
- 2:2604:02 - What do we do at Vonage?
- 4:0310:30 - Messaging Bus
- 10:3110:55 - Locust io
- 10:5618:53 - Types of load tests
- 18:5422:52 - Ios 13
- 22:5324:48 - Taking a bus ride with Shredder
- 25:4933:30 - QnA
related talks
39mBuilding an event-driven notification system in Go and RabbitMQ
25mIntelligent Notification Systems at Scale
48mBuilding a Distributed Data Ingestion System with RabbitMQ
24mAdvanced RabbitMQ Strategies: A case study
32mRabbitMQ in Real Life - Tips and Tricks
01h 05mScaling Applications with RabbitMQ
48mA Beginner's Guide to Inter-Service Messaging
53mMessaging: The fine line between awesome and awful