rabbitmq-shovel

how to use multiple configuration files for RabbitMQ / Erlang

↘锁芯ラ 提交于 2020-01-01 06:24:51
问题 I am trying to setup a Spring based Java application which uses a locally installed RabbitMQ server for delivering messages between nodes. As some of you already know, the rabbitmq.config file can be used to configure various parameters and is loaded by the underlying Erlang node which the Rabbit server runs on. My problem is that I have a requirement that some of the configuration needs to be static and some needs to be dynamic , specifically, I need to be able to reconfigure the shovels

RabbitMq Architecture for distributed POS

∥☆過路亽.° 提交于 2019-12-13 00:38:29
问题 We are developing a grocery Point of Sale system to replace an existing legacy system. We are evaluating using RabbitMQ for sending product/price changes down to the tills. A company may have anywhere from 1-50 stores, and each store may have 1-20 tills. Every till in the store will be receiving the same data. There will be one central backoffice per company. There will be a Rabbit broker at the backoffice, and at each store. In my current design, the backoffice broker has a queue setup for

RabbitMQ RPC across multiple rabbitMQ instances

安稳与你 提交于 2019-11-29 03:40:56
I have three clients each with their own RabbitMQ instances and I have an application (let's call it appA) that has its own RabbitMQ instance, the three client applications (app1, app2, app3) wants to make use of a service on appA. The service on appA requires RPC communication, app1, app2 and app3 each has a booking.request queue and a booking.response queue. With the shovel plugin, I can forward all booking.request messages from app1-3 to appA: Shovel1 virtualHost=appA, name=booking-request-shovel, sourceURI=amqp://userForApp1:password@app1-server/vhostForApp1 queue=booking.request

RabbitMQ RPC across multiple rabbitMQ instances

╄→尐↘猪︶ㄣ 提交于 2019-11-27 17:46:21
问题 I have three clients each with their own RabbitMQ instances and I have an application (let's call it appA) that has its own RabbitMQ instance, the three client applications (app1, app2, app3) wants to make use of a service on appA. The service on appA requires RPC communication, app1, app2 and app3 each has a booking.request queue and a booking.response queue. With the shovel plugin, I can forward all booking.request messages from app1-3 to appA: Shovel1 virtualHost=appA, name=booking-request