amqp VS RabbitMQ

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.

Although they did not make it into production, I experimented with the RabbitMQ message broker, Python (Django, Flask), Kubernetes + minikube, JWT, and NGINX. This was a hobby project, but I intended to learn about microservices along the way.

Messaging/Queueing Systems (Amazon SQS, RabbitMQ, Beanstalkd)

Later, we discovered Propan, a library created by Nikita Pastukhov, which solved similar problems but for RabbitMQ. Recognizing the potential for collaboration, we joined forces with Nikita to build a unified library that could work seamlessly with both Kafka and RabbitMQ. And that's how FastStream came to be—a solution born out of the need for simplicity and efficiency in microservices development.

Inter-Service Communication: Middleware provides communication channels and protocols that enable microservices to communicate with each other. This can include message brokers like RabbitMQ, Apache Kafka, RPC frameworks like gRPC, or RESTful APIs.

This is an implementation of pub/sub. The publisher is on a separate project. The message broker is Azure Service Bus. We use NServiceBus for code implementation. I use rabbitMQ broker for local tests. Nothing I can do about the tech stack. This is more of a high level single project structure review 😅

RabbitMQ is a robust and highly configurable open-source message broker that implements the Advanced Message Queuing Protocol (AMQP).

When using third-party services, especially within a "transaction", it's often a good idea to use a persistent Message Queue (MQ) system like RabbitMQ. Go through all their tutorials to get a really good understanding of how message queues work and how they can be used to solve your problem.

The best technical solution to provide the event queues is to use a message-broker technology like RabbitMQ.