RabbitMQ集群也包括可扩展性吗? [英] Is RabbitMQ Clustering including scalability too?

问题描述

我想构建一个RabbitMQ系统，该系统可以扩展以提高性能.

I want to build a RabbitMQ system which is able to scale out for the sake of performance.

我已经阅读了RabbitMQ Clustering的正式文档.但是，其群集似乎不支持可伸缩性.这是因为，即使可以从群集的任何节点访问主队列，也只能通过主队列进行发布/使用.除了主队列所在的节点之外，我们无法处理任何发布/消费.

I've gone through the official document of RabbitMQ Clustering. However, its clustering doesn't seem to support scalability. That's because only through master queue we can publish/consume, even though the master queue is reachable from any node of a cluster. Other than the node on which a master queue resides, we can't process any publish/consume.

我们为什么要聚类?

推荐答案

我们为什么要聚类?

Why do we cluster then?

• 为确保可用性.
• 强制执行数据复制.
• 将负载/数据跨队列分布在不同的节点上.主队列可以存储在不同的节点上，并且可以以小于< 1的因子进行复制.群集节点的数量.

除了主队列所在的节点外，我们无法处理任何发布/消费.

Other than the node on which a master queue resides, we can't process any publish/consume.

客户端可以连接到群集的任何节点上.该节点将请求"传输到主队列节点，反之亦然.作为缺点，它将产生额外的跃点.

Client can be connected on any node of the cluster. This node will transfer 'the request' to the master queue node and vice versa. As a downside it will generate extra hop.

这篇关于RabbitMQ集群也包括可扩展性吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！