Separate response queues for each client

The sequence below shows the interaction between the components of the application in a scenario when Client A updates a file that is shared with Client B and C, so they should receive the update too. If the other clients are not online at the time of the update, the Message Queuing Service keeps the update notifications in separate response queues for them until they come online later.

is there going to be a huge number of response queues. for example, let’s say there are 500 million users and 3 clients per user. then, there will be 1.5 billion response queues. is that going to be a problem?

1 Like