Riot Messaging Service - Message Players Like a Pro
summary
Riot Messaging Service is a stateful WebSocket router built in Erlang that moves JSON or binary payloads from backend services to players using REST for pub/sub, Docker on AWS, Terraform for infra, and Jepsen for fault injection. It scales linearly, claims 10 million connections on a single server in tests but production caps at 350,000 per box, uses ELB initially then service discovery, provides per-player routing, dynamic configs, health checks, and persisted delivery is planned.
AI-written summary · about
chapters (14)
- 0:00Introduction to Riot Games
- 2:50Challenges with the Old System
- 5:02Introduction to RMS
- 6:10RMS Functional Analogy
- 8:03Club Features and Workflow
- 13:06RMS Architectural Tiers
- 15:28Routing Tier Details
- 16:35Message Flow in System
- 17:23Technology and Tools
- 21:10Lessons in Distributed Systems
- 24:24Monitoring and Visibility
- 26:13Self-Service Capabilities
- 28:48Capacity Planning and Incident
- 31:35Future Plans and Q&A
related talks
39mScaling League of Legends Chat to 70 million Players
41mForget about HTTP
48mA Beginner's Guide to Inter-Service Messaging
25mTaming Client-Server Communication
49mCommunication in a microservice architecture
17mServiceRouter: Hyperscale and Minimal Cost Service Mesh
46mReal-world Examples of Message Queue Usage: Insights from RabbitMQ
32mRabbitMQ in Real Life - Tips and Tricks