We’re designing a brand new characteristic in our system the place shoppers (client == inner utility) must obtain messages about adjustments in objects they’re curious about.
From the statistics we gathered we see the maximal variety of objects a single client may be curious about is 50Okay (on common it might be ~15Okay).
Preliminary assessments exhibits that that is works OK and RabbitMQ handles it, however after we delete such a queue (if for instance we cutting down the system and shutting down one of many cases) it takes a couple of minutes for it to be deleted and the RabbitMQ administration portal turns into unresponsive.
Does it make sense to have so many bindings or is it a nasty design?
- We we’ll have round 50 cases of the shoppers, each with its personal queue which isn’t persistent and must be auto deleted when the buyer shut down