osbuild-composer VS RabbitMQ

Postgres can handle this well if you use pub/sub notification which is built-in. You can easily pick up jobs using a time-based where clause and it also scales well. There is no need to pull a complex library for this, here is a good example of such implementation.

I read through the following and I just wasn't sure if I wanted to spend time figuring out if it would work. https://github.com/osbuild/osbuild/issues/644 https://github.com/osbuild/osbuild-composer/issues/1411

The change to hash by default just landed upstream: https://github.com/osbuild/osbuild-composer/pull/2834

Based on this upstream issue and this draft pull request, osbuild-composer just doesn't support CentOS yet. To help indicate demand for this feature to the maintainers of that software, I suggest reproducing the error on CentOS Stream 8 and filing a bug as described here. Once the feature is implemented it will be available in CentOS Stream 8 first.

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.