Support for overlapping queue

[abraluve]

Hi,

right now I cant see support for overlapping IQueue mechanism.

Use-case:
3rd party app triggers twice API with same payload -> Web API creates 2 queue broadcasts -> 2 identical broadcast are running in same queue.

Goal is to have ability to check whether queue already contains specific Event with specific data.

[jamesmh]

This is a case where nonce or idempotency key in the 3rd party app's request would help. I don't think this is something that Coravel should implement as it's an issue of idempotency at the web / API level. For example, if you weren't using Coravel but were writing to a database in those web API actions, then you would potentially get 2 new database records for the "same" entity.

The only place that can determine whether the entity here is truly a duplicate is the client, at some level.

Let me know if that makes sense - thanks!

[abraluve]

Thanks for feedback.

We actually cant fix 3rd party app. My incoming API is light, adding to queue and immediatelly return empty response to do not block 3rd party app.. as it block 3rd party UI..

However they have bug there :/

So alternative fix for me would creating own queue that will e.g. run every 15 seconds and de-duplicate same data.

However it would be great to access IQueue tasks based on event and to access their data - only for readonly use.

[jamesmh]

It might be better to put that deduplication logic inside the handler method of the queued job. You can store the results either in a persistent storage or in shorter term cache. Then in the handler you can check "does this data already exist?"

You could even use Coravel's cache for this and cache that data for something like an hour or something.

Stripe does something like this with it's API - it stored idempotency keys for some hours before dropping them.