. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 36.4. Scaling Down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . note that while the goal of clustering is to increase overall message throughput via horizontal scaling it is not a "silver bullet." In certain situations clustering can, in fact, reduce message throughput know that a further hop away is node C which does have consumers. 32.8.3. Scaling Down Apache ActiveMQ Artemis supports scaling down a cluster with no message loss (even for non- durable messages). This

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231 36.4. Scaling Down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . note that while the goal of clustering is to increase overall message throughput via horizontal scaling it is not a "silver bullet." In certain situations clustering can, in fact, reduce message throughput know that a further hop away is node C which does have consumers. 32.8.3. Scaling Down Apache ActiveMQ Artemis supports scaling down a cluster with no message loss (even for non- durable messages). This

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 36.4. Scaling Down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . note that while the goal of clustering is to increase overall message throughput via horizontal scaling it is not a "silver bullet." In certain situations clustering can, in fact, reduce message throughput know that a further hop away is node C which does have consumers. 32.8.3. Scaling Down Apache ActiveMQ Artemis supports scaling down a cluster with no message loss (even for non- durable messages). This

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230 36.4. Scaling Down. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . note that while the goal of clustering is to increase overall message throughput via horizontal scaling it is not a "silver bullet." In certain situations clustering can, in fact, reduce message throughput know that a further hop away is node C which does have consumers. 32.8.3. Scaling Down Apache ActiveMQ Artemis supports scaling down a cluster with no message loss (even for non- durable messages). This

each other. Clustering was designed as a way to increase message throughput through horizontal scaling. The messages in a clustered queue can be spread across all nodes in the cluster. This allows clients disabled/off. Group Buckets For handling groups in a queue with bounded memory allowing better scaling of groups, you can enable group buckets, essentially the group id is hashed into a bucket instead is a poor choice because the fundamental ideas of grouped (i.e. ordered) messages and horizontal scaling through clustering are essentially at odds with each other. Message grouping enforces ordered message

each other. Clustering was designed as a way to increase message throughput through horizontal scaling. The messages in a clustered queue can be spread across all nodes in the cluster. This allows clients disabled/off. Group Buckets For handling groups in a queue with bounded memory allowing better scaling of groups, you can enable group buckets, essentially the group id is hashed into a bucket instead is a poor choice because the fundamental ideas of grouped (i.e. ordered) messages and horizontal scaling through clustering are essentially at odds with each other. Message grouping enforces ordered message

disabled/off. Group Buckets For handling groups in a queue with bounded memory allowing better scaling of groups, you can enable group buckets, essentially the group id is hashed into a bucket instead is a poor choice because the fundamental ideas of grouped (i.e. ordered) messages and horizontal scaling through clustering are essentially at odds with each other. Message grouping enforces ordered message messages in each group cannot be consumed concurrently which defeats the purpose of horizontal scaling. If you've evaluated your overall use-case with these design caveats in mind and determined that

note that while the goal of clustering is to increase overall message throughput via horizontal scaling it is not a "silver bullet." In certain situations clustering can, in fact, reduce message throughput know that a further hop away is node C which does have consumers. 32.8.3. Scaling Down Apache ActiveMQ Artemis supports scaling down a cluster with no message loss (even for non- durable messages). This size of a cluster may change relatively frequently. When scaling up a cluster (i.e. adding nodes) there is no risk of message loss, but when scaling down a cluster (i.e. removing nodes) the messages on

note that while the goal of clustering is to increase overall message throughput via horizontal scaling it is not a "silver bullet." In certain situations clustering can, in fact, reduce message throughput know that a further hop away is node C which does have consumers. 31.8.3. Scaling Down Apache ActiveMQ Artemis supports scaling down a cluster with no message loss (even for non- durable messages). This size of a cluster may change relatively frequently. When scaling up a cluster (i.e. adding nodes) there is no risk of message loss, but when scaling down a cluster (i.e. removing nodes) the messages on

note that while the goal of clustering is to increase overall message throughput via horizontal scaling it is not a "silver bullet." In certain situations clustering can, in fact, reduce message throughput know that a further hop away is node C which does have consumers. 31.8.3. Scaling Down Apache ActiveMQ Artemis supports scaling down a cluster with no message loss (even for non- durable messages). This size of a cluster may change relatively frequently. When scaling up a cluster (i.e. adding nodes) there is no risk of message loss, but when scaling down a cluster (i.e. removing nodes) the messages on