I addressed your question about global order on the other thread whose subject is "Global Order + Cluster + Message Redistribution." In short, "global order" and "high traffic/volume" are essentially at odds with each other. If you really want global order then don't cluster. If you want high volume then ditch global ordering and create a cluster.
That said, a single instance of ActiveMQ Artemis can potentially process millions of messages per second so you may not even need a cluster to deal with your volume. Have you benchmarked your application with real-world data content/volume and concluded that a cluster is necessary to deal with it? If not, that would be a worthwhile exercise. I've seen lots of users simply assume that they need to cluster when they really don't which complicates their architecture and wastes lots of resources. Justin On Fri, Dec 13, 2019 at 11:02 AM ldebello <[email protected]> wrote: > I got your point, after analyzing the result it seems when connecting to a > different broker is first doing the message aggregation/redistribution and > then providing the message to consumer. > > Given the fact clustering is something good to scale out and LVQ is > something like a good feature, I was thinking if would be possible to have > some property for LVQ cases to guarantee global order in cluster mode and > always keeping the "real" last value message. Maybe this property could be > fill up by the producer to allow ordering before replacing last value. > > I like the idea of clustering for scalability or could you share which > strategy use for high traffic/volumen? > > Thanks & Best Regards, > Luis > > > > -- > Sent from: > http://activemq.2283324.n4.nabble.com/ActiveMQ-User-f2341805.html > >
