amqp091-go VS amqp

For rabbitmq I used -> https://github.com/streadway/amqp which is deprecated now for -> https://github.com/rabbitmq/amqp091-go

Elasticsearch client for Go RabbitMQ Go RabbitMQ Client Library Jaeger open source, end-to-end distributed tracing Prometheus monitoring and alerting Grafana for to compose observability dashboards with everything from Prometheus Echo web framework Kibana is user interface that lets you visualize your Elasticsearch Docker and docker-compose Kubernetes K8s Helm The package manager for Kubernetes

Basically this code, connects to our rabbitmQ using the streadway/amqp package which is the golang standard library for communicating with rabbitmQ, next we declare a unique channel to enable us pass across message to a specific queue. Then we call the Consume function which takes in a parameter of *amqp.Channel which is the channel we created previously.

For rabbitmq I used -> https://github.com/streadway/amqp which is deprecated now for -> https://github.com/rabbitmq/amqp091-go

"github.com/streadway/amqp"

I’d also recommend looking into learning Go. I’ve been using this library and it’s great.

We're currently using streadway/amqp as RabbitMQ client library. It is well-documented and very stable on the one hand, but on the other hand, it is pretty low-level and leaves up a lot of things to the user. For example, we're in charge of handling the connections and channels ourselves and implemented our very own error handling and reconnection logic as well.

AMQP is a messaging protocol most commonly used by RabbitMQ. As I discuss in the README, the officially sanctioned RabbitMQ driver, streadway/amqp isamazing but does not support automatic redials. If your connection to the message broker goes down, you have to find a way to distribute a new connection to all routines utilizing it. It's always a tedious exercisee, especially when you have multiple projects that work with RabbitMQ.