RabbitMQ 4.0

Post by bdcravens » Thu, Sep 19, 2024, 10:13 AM UTC

Alupis wrote: post #70

infecto wrote: post #69

Earlier quoted context omitted.

I think it is fairly clear. If you are building a product of passion that you may tinker with for years, by all means cut costs as much as possible. If you are an actual early stage venture I don't believe those costs meet a high enough threshold to matter.

It depends, as things usually do. $20 here, $10 there, eventually ends up as $600 monthly or more, and no customer anywhere in sight. That may, or may not be sustainable or make sense. Flush with cash? Knock yourself out. Bootstrapping? You can spend that money a lot more effectively than just loading up on a bunch of overpriced SaaS products to make life easier. You have to earn the easy route by growing your revenu…

Post by rjh29 » Thu, Sep 19, 2024, 10:33 AM UTC

stackskipton wrote: post #23

fidotron wrote: post #3

I've regarded RabbitMQ as a secret weapon in plain sight for years. The killer reason people don't use it more is it "doesn't scale" to truly enormous sizes, but for anyone with less than a million users it's great. Too many people end up with their own half rolled pubsub via things like grpc, and they'd be far better off using this, particularly in the early stages of development.

Also want to give a shoutout to BeanStalkd: https://github.com/beanstalkd/beanstalkd If you are looking at RabbitMQ with "Maybe this is too much". Beanstalkd likely has features you need with almost none of the setup. Just don't web expose it ;)

Post by raverbashing » Thu, Sep 19, 2024, 12:35 PM UTC

leetharris wrote: post #4

fidotron wrote: post #3

I've regarded RabbitMQ as a secret weapon in plain sight for years. The killer reason people don't use it more is it "doesn't scale" to truly enormous sizes, but for anyone with less than a million users it's great. Too many people end up with their own half rolled pubsub via things like grpc, and they'd be far better off using this, particularly in the early stages of development.

This is how I feel about NATS: https://nats.io/ It's an infinitely more friendly version of Kafka, pub/sub, etc that is extremely lightweight. Yet every environment trends towards Kafka because it was "chosen" by the big corps.

Post by ofrzeta » Thu, Sep 19, 2024, 2:49 PM UTC

rodrigobellusci wrote: post #36

fidotron wrote: post #3

I've regarded RabbitMQ as a secret weapon in plain sight for years. The killer reason people don't use it more is it "doesn't scale" to truly enormous sizes, but for anyone with less than a million users it's great. Too many people end up with their own half rolled pubsub via things like grpc, and they'd be far better off using this, particularly in the early stages of development.

Do you know of any book or video to get started with Rabbit? Earlier this year I tried setting it up as a websockets message broker in a Spring Boot app but failed miserably. I ended up using Spring’s simple broker.

Post by hyperadvanced » Thu, Sep 19, 2024, 3:30 PM UTC

Karrot_Kream wrote: post #21

hyperadvanced wrote: post #14

Earlier quoted context omitted.

Have used both extensively: NATS, especially in its most elementary form, is braindead simple, stateless, and ootb functional. If I only want a message broker/pubsub, I pick that. If I know on day 1 that I need queues or persistence, I would probably pick Rabbit over NATS’ offering (Jetstream).

Would you use NATS over Redis PubSub or Postgres Notify/Listen? Postgres's option I'm wary of for reasons I've discussed here before but Redis PubSub seems fairly simple to use and likewise not as uber-scalable as Kafka and other more heavyweight message broker systems.