I'm a DevOps engineer with a team that uses rabbitmq heavily in their legacy applications. While it's okay for small scale projects, it's not ideal for anything production or large scale. If the host crashes, you lose all the messages in the Q, if your architecture doesn't consider this and you can't redrive what you lost there's no way you can sustain.
Ideally such people should consider a managed queuing service like Sqs in AWS and others in other cloud providers.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'm a DevOps engineer with a team that uses rabbitmq heavily in their legacy applications. While it's okay for small scale projects, it's not ideal for anything production or large scale. If the host crashes, you lose all the messages in the Q, if your architecture doesn't consider this and you can't redrive what you lost there's no way you can sustain.
Ideally such people should consider a managed queuing service like Sqs in AWS and others in other cloud providers.