>Very few technical problems don’t have any elasticity in outflows, They have elasticity but you don't care for it. You run it at the maximum. As you mentioned

>Very few technical problems don’t have any elasticity in outflows, They have elasticity but you don't care for it. You run it at the maximum. As you mentioned the only case where you wouldn't is if you have some transaction that doesn't scale linearly with with frames/events. >Given the common use case of batching, which inherently requires items to be queued for a period of time, how can you say that queues should always be empty? They would statistically rarely be empty. Which is a good thing. Because it enables batching. In my experience, while batching is not uncommon, streaming is the much more common use case. So we can agree to disagree here.