amazon-sqs-java-messaging-lib VS RabbitMQ

Save to SQS (i.e. save each Event to Amazon’s SQS queuing service)

Amazon SQS

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

The last stage is productionizing the model. The goal of this phase is to create a system to process each image/video, gather the relevant features and inputs to the models, integrate the models into a hosting service, and relay the corresponding model predictions to downstream consumers like the MCF system. We used an existing Safety service, Content Classification Service, to implement the aforementioned system and added two specialized queues for our processing and various service integrations. To use the model for online, synchronous inference, we added it to Gazette, Reddit’s internal ML inference service. Once all the components were up and running, our final step was to run A/B tests on Reddit to understand the live impact on areas like user engagement before finalizing the entire detection system.

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.