It's due to limitations and resiliency of the product, but it isn't necessarily "300 concurrent = br
It's due to limitations and resiliency of the product, but it isn't necessarily "300 concurrent = break", it's more nuanced than that. If you aren't able to work around the issue with retries or bucket sharding then I'm afraid that may mean that the product isn't currently well suited to your use-case
