> The hot path (... list) are all served by synchronous API servers Wait; how does that work, when a user is PUTting tons of objects concurrently into a bucket

> The hot path (... list) are all served by synchronous API servers Wait; how does that work, when a user is PUTting tons of objects concurrently into a bucket, and then LISTing the bucket during that? If the PUTs are all hitting different indexing-cluster nodes, then...? (Or do you mean that there are queues/workers, but only outside the hot path; with hot-path requests emitting events that then get chewed through async to do things like cross-shard bucket metadata replication?)