Anycable - Universal Action Cable
summary
AnyCable extracts Action Cable’s low‑level WebSocket server into a separate service and proxies protocol commands over gRPC/protobuf so Rails keeps existing channels and the JS client. Implementations in Go and Erlang show much lower memory and CPU: benchmarks move from multi‑second broadcast latency with 16 Ruby workers to sub‑half‑second rebroadcasts at thousands of connections, and ~4x lower resource cost. Production use reports thousands (not millions) of connections, easier zero‑downtime deploys, and room to add fallbacks, metrics and history streams.
AI-written summary · about
chapters (15)
- 0:00Introduction of the speaker
- 2:42What is Action Cable
- 5:33Pros and cons of Action Cable
- 7:23Limitations of Action Cable
- 8:30Memory usage in Action Cable
- 10:15Performance benchmarks
- 14:17Introducing AnyCable
- 17:54How AnyCable works
- 19:01AnyCable benchmarks
- 21:13Live demonstration
- 23:00Light Cable for non-Rails apps
- 24:50Additional AnyCable features
- 28:01Deployment benefits
- 31:15Future of AnyCable
- 31:37Production use and Q&A
related talks
34mUnraveling the Cable: How ActionCable works
39mActionCable for Not-Another-Chat-App-Please
35mEvolution of Real-Time and AnyCable Pro and ... me
28mReal-time collaboration with Rails
38mHigh Concurrent Ruby Web Development Without Fear
35mThe Action Cable Symphony - An Illustrated Musical Adventure
47mActionCable, Rails API and React - Modern Single Page Apps
28mReal-Time Rails