termux-widget VS RabbitMQ

Install Termux, Termux Widget, Termux Tasker on F-droid or on the official Termux Github repository.

I use it termux mainly to ssh to a server but also to ssh from my laptop to the phone by running sshd inside termux. By using scp and with the right ssh host config and authorized_keys I can send and receive files across devices, really useful when devices are on the same VPN but not on the same network.

I also use Termux:Widget [1] to launch scripts. For example, I have added all my contacts to abook [2], and with a bash script that use fzf I can filter my contacts and it automatically get the contact gps field and automatically start the navigation.

[1]https://github.com/termux/termux-widget

[2] https://abook.sourceforge.io/

Please do some research on your own. Start here

[^2]:[Github Termux Widget](https://github.com/termux/termux-widget)

From Github Termux, Github Termux Widget download the APKs and install them.

Today, I will discuss some things that need to be considered to have a kind of reliable server when using Rabbitmq as a message broker.

Choose a consistent communication protocol for inter-service communication. Common protocols include HTTP, gRPC, and message brokers like RabbitMQ or Kafka. NestJS supports various communication strategies, allowing you to choose the one that best fits your needs.

Some simple best practices around performing RabbitMQ upgrades.

ℹ️ Manage quorum queues easily by using the rabbitmq-queues CLI. Here are some useful CLI commands.

RabbitMQ is an open-source message broker that implements the Advanced Message Queuing Protocol (AMQP). Its primary purpose is to facilitate reliable and efficient communication between different components of a distributed system. RabbitMQ acts as an intermediary, receiving messages from producers and forwarding them to consumers, ensuring that messages are delivered even if the receiving application is temporarily unavailable.

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 😅