[HN Gopher] RabbitMQ 3.11 Feature Preview: Super Streams
       ___________________________________________________________________
        
       RabbitMQ 3.11 Feature Preview: Super Streams
        
       Author : codeadict
       Score  : 34 points
       Date   : 2022-07-13 20:16 UTC (2 hours ago)
        
 (HTM) web link (blog.rabbitmq.com)
 (TXT) w3m dump (blog.rabbitmq.com)
        
       | FridgeSeal wrote:
       | A bit of a weird article. It announces super streams-which are
       | basically topic partitions in Kafka, acknowledges that, but then
       | hand-waves "oh but they're different" and then spends the rest of
       | the article talking about all the features that are identical to
       | how topic partitions work...
       | 
       | It's a good feature, there's nothing wrong with that, but there's
       | nothing wrong with saying "we've brought this feature to RabbitMQ
       | too" rather than trying to pretend it's totally-not-the-same.
        
       | kungfufrog wrote:
       | If I had to nominate a piece of software, as an SRE, that is as
       | close to "set and forget" as possible, it'd absolutely be
       | RabbitMQ standalone and a close runner up would be its clustered
       | form.
       | 
       | I've worked in 3 places where RabbitMQ has been a fundamental
       | cornerstone of the architecture, and while it does require a
       | little tuning around performance occasionally (generally because
       | it's being used inappropriately or without full consideration of
       | its limitations/best practices), it's rock solid, easy to
       | debug/inspect, has an active and supportive community, and is
       | generally just all around pleasant to work with and maintain.
       | 
       | Kudos to RabbitMQ and its developers!
       | 
       | As an aside, the addition of recent features such as super
       | streams, streams and quorum queues make it a compelling all-in-
       | one tool for solving a bunch of architectural based
       | concerns/requirements in application and infrastructure
       | development. I've often thought about why it's not more utilised
       | in the ops side of the world for metrics gathering and other
       | usecases. I have also wondered how useful it'd be for log
       | ingestion with lazy queues etc.
       | 
       | Does anyone out there have examples of unusual use cases for
       | RabbitMQ where it's outshone some alternative product? Would love
       | to hear about them!
        
         | dalyons wrote:
         | interesting, i have the opposite experience. When we got to
         | high throughput in a cluster we had all sorts of crashes,
         | partitions, and nasty failure modes that required stressful
         | delicate rebuilds. It has similar challenges to a clustered M-M
         | relational db. Moved the high volume events to kinesis which
         | was far more reliable for that use case.
         | 
         | At low volumes yeah sure, it just ticks along, and does what
         | you want.
        
         | jsmeaton wrote:
         | I feel like "and while it does require a little tuning around
         | performance occasionally" is doing a lot of heavy lifting there
         | :)
         | 
         | Honestly though my only experience with RabbitMQ has been as a
         | backend for Celery (background task processor for Python) and I
         | think my real issues are mostly to do with how Celery uses
         | RabbitMQ in a very poor default setup.
         | 
         | Message confirmations are off by default and turning them on
         | caused our queues to grind to a halt. Queues being single
         | threaded and clusters don't much help with that without using
         | some kind of sharding plugin. It seemed like getting to a good
         | spot required a lot of arcane knowledge that wasn't so easy to
         | find.
         | 
         | "Configuring RabbitMQ to be a performant message queue for
         | background task systems" would be an excellent blog post I
         | would share widely!
        
       ___________________________________________________________________
       (page generated 2022-07-13 23:00 UTC)