thanks for the reply but for the queue based messaging， there's an implicit requirement - Load Balancing
To conclude my requirement 1. only one subscriber received the msg, but not to broadcast and let subscribers synchronously decide who will process it, which wastes network resource unneccessarily 2. subscribers are also clustered, means there is Load Balance, just like how we use RabbitMQ queue without topic My plan B is to use the distributed data structure "QUEUE", and let all subscribers loop to snatch message. I also think about calling service deployed in service asynchronously，but considering back pressure, this approch won't work. So it's confirmed that ignite doesnt have a queue based messaging, and I have to go for my plan B? -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
