RabbitMQ - federated queues Vs exchange federation -


i have set rabbit cluster , publish messages fanout exchange every time changes in database.

i have dedicated queues bound exchange of microservices consume these updates , set dedicated queue external client can federate own rabbit infrastructure , consume copy of every message.

now i'm wondering whether allowing exchange federation rather creating new dedicated queue each new external consumer better approach since more , more users come.

what pros , cons?

thanks

as long manage permissions properly, final decision you. can give try variants first , find fit actual needs.

having local queue may have pros , cons: allows end-user survive outage infrastructure or network issue @ cost of disk/memory, however, may limit queue length and/or size.

i'd suggest take @ shovel plugin , dynamic shovels. local queue may server job.

comparing federation, shovel simpler, e.g. doesn't sync content between upstream , downstream moves message 1 queue in reliable manner. long don't need federation provides, shovel choice.

also, may find q/a useful (however, might bit outdated) - https://stackoverflow.com/a/19357272.


Comments

Popular posts from this blog

javascript - Clear button on addentry page doesn't work -

python - Error: Unresolved reference 'selenium' What is the reason? -

asp.net ajax - Jquery scroll to element just goes to top of page -