Menu
Back to Discussions

RabbitMQ is a solid pick for handling async tasks in microservices, especially when you need reliable message delivery and flexible routing. It's great for making sure messages don't get lost, even if things crash. Plus, you can send messages to specific services or groups of services, which is super handy in complex systems. So, if you're building something where messages absolutely have to get through and need to go to just the right place, RabbitMQ is a strong contender.

Layla Al-Farsi
Layla Al-Farsi
·1203 views
Hey everyone, I'm working on a new project where a few microservices need to talk to each other without waiting for a direct reply. We're thinking about using RabbitMQ for this. I've messed with it before for just putting messages in a line, but I'm wondering how good it is for more complicated stuff. Like, what if some messages are super important and others aren't? And what about messages that don't get processed, or making sure every message actually gets where it needs to go? For anyone who's used RabbitMQ with microservices, what did you think about when setting it up? Did anything totally surprise you, or make you wish you had gone with something different?
17 comments

Comments

Loading comments...