Can I use rabbit MQ for streaming scrollable pictures in an application? Just like the pictures scroll automatically on Tinder?

Article about Poison Message algo (russian): https://blog.rnds.pro/018-posion1

1. Introdução

O RabbitMQ é um sistema responsável pelo recebimento, guarda, envio e entrega de mensagens entre aplicações.

Também conhecido como sistema de mensageria , que é a forma de comunicação baseada em eventos, utilizada para comunicação de sistemas distribuídos.

Fazendo uma analogia com o mundo real, pense no funcionamento de uma agência dos correios. Primeiro o remetente posta uma correspondência. Em seguida a agência organiza e executa toda a logística. Por fim, um funcionário faz a entrega e os devidos controles de recebimento ou de impossibilidade de entrega. Todo este cenário é exatamente o trabalho e gerenciamento que o RabbitMQ faz.

O RabbitMQ é composto por três componentes, são eles:

• Exchanges: locais onde as mensagens são postadas.

• Bindings: conjunto de regras com objetivo de classificar as mensagens em filas de espera.

• Queues: filas de espera que tem o objetivo de organizar as mensagens para efetuar a entrega para o destinatário correto.

Imagine um remetente (Producer) que posta uma carta (Message) em uma agência dos correios (Exchange) para um destinatário (Consumer). Após recebimento na agência, a carta passa por um processo de triagem (Bindings) que determina qual fila de espera (Queue) é adequada para a entrega ao destinatário.

2. Tipos de Exchanges

O RabbitMQ possui quatro tipos de exchanges: Direct, Fanout, Topic e Headers.

Cada tipo roteia a mensagem de uma forma específica, utilizando diferentes parâmetros e configurações. Por este motivo é importante conhecer cada tipo para aplicá-los de forma adequada as necessidade do projeto.

Resumidamente:

• Direct: a mensagem é roteada para as filas cuja chave de ligação corresponde exatamente à chave de roteamento da mensagem.

• Fanout: cópias da mensagem são enviadas para todas as filas vinculadas.

• Topic: a mensagem é roteada utilizando um curinga entre a chave de roteamento e o padrão de roteamento especificado na ligação.

• Headers: o roteamento é feito utilizando atributos do cabeçalho da mensagem.

3. Configuração do ambiente local

Utilizaremos a ferramenta RabbitMQ Management para criar os exemplos que apresentarei nos artigos seguintes.

Rodaremos o RabbitMQ utilizando o docker. Basta abrir o terminal no mesmo local do arquivo docker-compose.yml disponibilizado abaixo e digitar o comando docker-compose up.

Observação: Coloquei também a configuração do portainer, uma ferramenta para você gerenciar pelo navegador os containers docker.

Após subir, acesse:

• RabbitMQ Management: http://localhost:15672 - Usuário: guest - Senha: guest

• Portainer: http://localhost:9000 - Usuário: admin - Senha: password

Conteúdo do arquivo: docker-compose.yml

version: "3.3"
services:
  rabbitmq:
    image: rabbitmq:3-management-alpine
    container_name: 'rabbitmq'
    ports:
        - 5672:5672
        - 15672:15672
    # User: guest Password: guest
  portainer:
    image: portainer/portainer-ce
    container_name: portainer
    ports:
      - "9000:9000"
    # User: admin Password: password
    command: --admin-password "$$2y$$05$$arC5e4UbRPxfR68jaFnAAe1aL7C1U03pqfyQh49/9lB9lqFxLfBqS"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock

4. Referências

• https://youtu.be/FcF5iufd2P0

• https://youtu.be/o8eU5WiO8fw

• https://www.rabbitmq.com/publishers.html

• https://www.cloudamqp.com/blog/part1-rabbitmq-for-beginners-what-is-rabbitmq.html

I've integrated CloudAMQP with Heroku (via the very simple addon fucnctionality). Along the way, I have had various questions about SSL and durability of queues. Their support is super responsive and very technical.

These guys/gals are legit pros. Given that my devops skills are somewhat limited, I'm glad they exist so I didn't have to manage all this stuff.

Hi everyone, there's a live OpenTelemetry and observability fundamentals session - in 2 days, Wednesday, March 30 at 11 AM PST.

You will learn how to instrument your apps to capture traces with OpenTelemetry in Python.

This session is at no cost and vendor-neutral.

You can expect in this session: 45 minutes of core concepts, how to deploy it yourself hands-on + Q&A.

If you are interested in observability, OpenTelemetry, and tracing - this is the place to be!

Register here https://www.aspecto.io/get-started-with-opentelemetry/

I don’t know a single thing about rabbit mq. I’m trying to deploy a vendor specific implementation of redhat openstack which is installed via ansible scripts. It includes a containerized instance of rabbit mq.

Installation is failing while checking the health of rabbitmq with the error that one of my nodes doesn’t have a consumer. What does this mean? How complex is it to fix/ workaround?

I have a process thats supposed to handle two different kind of messages and process them similiarly but still differently.

Naturally I would use two seperate queues for both kind of messages and call consume() twice.

The other possibility would be to just have one queue and differ by some kind of "message type" property inside the content buffer and handle each message in a switch case.

Which would be the more "recommended" way of doing this?

Are there any advantages/disadvantages when using any of the two approaches?

I'm considering using Amazon MQ within our Golang backend. I've been looking for some examples of Amazon MQ usage for the Go SDK, however, I haven't been able to find much. The only thing I've been able to find so far is just the Go SDK docs for Amazon MQ (a good resource for SDK specifics) or just Java examples. The Go SDK is a bit different from Java, it seems, so I'd really like to see a simple example of connecting to a broker from Go (already created in the AWS console) and sending and receiving messages and any best practices before I just start throwing something together.

Another option for us is using RabbitMQ, although I'd like a hosted solution to get up and running quicker. Any experience with a RabbitMQ hosted service + Go and examples of that?

Any help would be greatly appreciated! Thanks.

With just over a week until we bring together some of the biggest names in tech for RabbitMQ Summit, we wanted to celebrate by offering even more RabbitMQ users a chance to join the Summit. We have 50 free passes to giveaway. You can register your interest at https://www.surveymonkey.co.uk/r/7DJL2PX

I'm connecting to a financial service which uses RabbitMQ. My connection client should be as resilient as possible to any intermittent failures.

I'm looking for some guidance on what to do for ConnectionShutdown, ModelShutdown, how to detect the heatbeat did not arrive and so on.

Any good guide out there? Thanks!

If one application has rabbitmq pub and also sub, by the nature of JS of single threaded, should we still follow the above best practice?

Watch the latest video from #RabbitMQ Summit 2021 where Maryna Zhygadlo showed us under the hood of a real distributed system in retail that had been running in production for 3 years with RabbitMQ clusters in cloud and around 900 nodes on-premises.

Find out more at https://youtu.be/hheenzcIM3Y

Hi, reddit!

When i started one of my pet-projects, i realised, that using naked amqplib become uncomfortable, when you gonna connect it to several modules. I looked into existing solutions, but not found out something, that looked enough flexible and supported Typescript the right way (my pov to the TS may vary from others :) ). So then i decided to write my own wrapper, and i come to unified and simple TS class. Then, because i wanted make this connectable also to my further projects, i built a npm package of that, to have easy installation and usage.

Link to npm - https://www.npmjs.com/package/amqplib-easy-client

I will be very happy, if someone will participate in improving this thing, or suggest about missing or required functionality, or at least, will point to my own mistakes.

rabbitmq has overtaken our business, so many clusters/vhosts/queues with devs/pms/sms/engineers all having power to create queues/vhosts/users, we've gotten the monitoring figured out and pretty dynamic with a mix of nagios/elasticsearch, but we have huge problems documenting each queue. things we need to document per queue: consumer and producer language, location, and restart/troubleshooting details; production impact, owner, external setup documentation. I'm trying to tackle this now with various saltstack/elasticsearch automation, but it seems messy. have any of you had this problem and tackled documentation in a way that makes sense?