Data Stores Service protection measures affecting data downloads and account access (CDS/ADS/EWDS/ECDS)

I’m happy with all of these points except the one about sequential requests. Isn’t that exactly what a queueing system is for? If parallel requests are a problem, why not limit the number of active requests per user on the CDS side?

We maintain an application that submits its requests in parallel. Because of the new request size limits (403 Client Error while downloading 1 day of Europe constrained ERA5 data - #9 by Michela), one day of ERA5 model level data already takes 4 separate requests, so even a modest case quickly adds up to a few dozen. Are you really asking us to build our own queueing system as a new layer on top of the CDS?!

At the very least, could you say what counts as “parallel or in large batches”? How many active or queued requests per user is acceptable before an account gets flagged? Without that, every user who submits more than one request at a time risks being suspended.