Avito Messenger Architecture – The Journey of a Single Message
summary
Describes Avito's large-scale messenger architecture: how a message travels from sender to recipient through the chain of services, including deployment practices, data storage in MongoDB, and queue patterns using RabbitMQ. Gives concrete service load figures (11M monthly users, ~25k RPC/s, 500k concurrent connections peak) and focuses on system design and operational patterns for high-throughput messaging.
AI-written summary · about
chapters (10)
- 0:00Architecture introduction
- 3:38Messenger evolution
- 8:38Socket service and WebSocket
- 12:10Aggregator service and grace degradation
- 16:29Async message processing
- 23:13Real-time modifications and Redis Streams
- 30:23Migration to Redis Streams
- 38:18Architecture drawbacks
- 41:06Conclusions and recommendations
- 42:08Q&A
related talks
53mFrom Click to Publish: Architecture of Avito’s Classifieds Platform
51mAPI Gateway at Avito
58mAvito Data Store: Analytics for a Microservices Architecture
49mExperience running a Service Mesh at Avito
53mMessaging: The fine line between awesome and awful
48mA Beginner's Guide to Inter-Service Messaging
49mCommunication in a microservice architecture
49mActiveMQ - Journey to 1 Billion msg/day