What's New in RabbitMQ Streams?
summary
Streams are a new persistent, replicated log in RabbitMQ that reached production parity after a year, claiming up to 1 million messages per second on a three-node cluster by batching and zero-copy sendfile delivery; clients exist for Java, .NET and Go with community libraries for Python, Elixir and JavaScript; 3.11 adds single active consumer for failover and super streams (partitioned streams) to scale consumption, with replication using quorum-style acknowledgements and TLS for inter-node replication.
AI-written summary · about
chapters (14)
- 0:00RabbitMQ Streams intro
- 1:53Streams vs queues
- 6:30Stream protocol benefits
- 10:50Streams in 3.10
- 13:42Client libraries growth
- 15:33New features 3.11
- 16:36Single Active Consumer
- 19:34Super Streams intro
- 24:25Super Streams balancing
- 29:03Future plans
- 31:09Q&A: Consumer guarantees
- 34:03Q&A: Protocol performance
- 38:00Q&A: Replication consistency
- 40:14Q&A: SAC enforcement
related talks
50mPanel discussion: The new RabbitMQ Streams
50mIntroducing Stream Support in RabbitMQ
26mBreaking Magical Barriers
59mGame of Streams: How to Tame & Get the Most from your Messaging Platforms
57mGame of Streams: How to Tame and Get the Most from Your Messaging Platforms
37mLet's build our own message streaming platform
37mImplementing Raft in RabbitMQ
48mStreaming all the things with Akka Streams
