devspace VS RabbitMQ

Check also devspace.sh and okteto.com

There is actually a built-in converter from docker-compose.yaml to devspace.yaml, it is part of the "devspace init" command. There are a few known issues related to it, in case you would like to contribute :)

Wrapping https://devspace.sh in my company's internal CLI to improve development experience

For Kubernetes clusters, https://devspace.sh/ allows you to iterate on your app in a running pod from your IDE. No ci/cd pipeline, no re-applying manifests; it just uploads source code from your local machine and restarts your app for you in an existing pod. Pretty slick!!! But it requires K8s, so some devs may balk at it. (Tilt and Skaffold do the same thing)

We’re excited to announce that DevSpace version 6 has been released. Thanks to everyone who used the alpha and beta versions and gave us feedback.

DevSpace is free, lets you develop natively in the cloud on any K8s cluster. Compatible with any multitenancy solution, policy governance, etc. Works with your IDE of choice. Declarative configuration. Supports custom pipelines and deploy logic. Can link multiple environments together. https://devspace.sh/

My favourite tool in this category is Devspace. As you've requested it is capable of building and deploying multiple images.

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.