Once message is consumed, it removed from queue and it can’t be read by another consumer.
You can achieve this by sending the message to multiple queues.
Message from the same queue can’t be consumed by multiple consumer.
Yes. This correct. if the message is sent to different queues, then it can be consumed by different consumer. But I wouldn’t call it same message. Maybe same message logically.
But let’s say it more accurate: Message in the same queue can’t be consumed by many consumers.
I’m happy that at least you find something useful…
But regrading your concerns, I gave an example of item that is going to be deleted. the item is first deleted from the collection and not seen anymore in the UI, but if the operation fail later, like server error occurred, Then I have to re-add it to the collection, and not…
If child components don’t have a real router path in the router config. This solution won’t work for it. But I think this can work if you will do that for parent component. Or by creating routing path for that child components