Hiram, We have to protect our brokers from misbehaving clients. The most simple case is a consumer that does not consume the messages in its queues (or durable subscriptions), wasting disk space, until it affects other clients (disk/partition full).
Message expiration does help but only really works with constant message rates and sizes. It would be very good to have per-destinations quotas (at least using a message count but a total message size would be useful too) and have the broker deleting the oldest not yet consumed messages when needed. This way, the queues with quotas would become some kind of rings, using limited disk space. Do you think it's something Apollo could do? Cheers, Lionel
