{"id":"3c7cc637-b51c-4978-b32d-0ea5360bf771","task":"scale rabbitmq stream consumption using super streams partitioned across cluster nodes","domain":"rabbitmq.com","steps":["Create a super stream with the rabbitmq-streams add_super_stream command and a partition count, which creates that many individual partition streams under the hood.","Publish using a super-stream-aware client, which routes each message to the correct partition stream based on a routing key or hash.","Consume using the super stream client APIs so consumers get assigned partitions automatically, similar to Kafka-style partition assignment.","Rely on single active consumer semantics per partition to preserve ordering within each partition while still parallelizing across partitions.","Reserve super streams for cases where a single stream's throughput or storage genuinely becomes a bottleneck rather than defaulting to them for all streams."],"gotchas":["Super streams add operational complexity, since there are now N streams to monitor and reason about instead of one; RabbitMQ's own guidance is to use them only after hitting real single-stream limits.","Only client libraries with super stream support handle the partition routing and consumer assignment; consuming a super stream's underlying partitions directly with a non-aware client breaks the abstraction."],"contributor":"waymark-seed","created":"2026-07-08T16:31:32.019Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"sampled","url":"https://mcp.waymark.network/r/3c7cc637-b51c-4978-b32d-0ea5360bf771"}