We use queues to aggregate calls to an external API, only thing that would make queues for that use-
We use queues to aggregate calls to an external API, only thing that would make queues for that use-case better is that batches currently cannot be grouped by a (custom) identifier - say we scope all the data to a single customer and group it under a 30s queue timeframe, we could have more efficient calls to the external API (since they also operate under a per-customer/ID resource scope).
This is relevant because the external API has relatively strict account rate-limits (not scoped to the ID).
Right now it's hit or miss since possibly 100 different customers could join the same batch effectively resulting in groups of 1 and thus 100 API calls.
In this case we would prefer grouped batching over quick execution of a random batch if you understand what I mean
This is relevant because the external API has relatively strict account rate-limits (not scoped to the ID).
Right now it's hit or miss since possibly 100 different customers could join the same batch effectively resulting in groups of 1 and thus 100 API calls.
In this case we would prefer grouped batching over quick execution of a random batch if you understand what I mean
