Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aggregated Queue Job - Event changes delay the event further so it only fires once #1705

Open
bkuhl opened this issue Jul 4, 2019 · 1 comment

Comments

Projects
None yet
2 participants
@bkuhl
Copy link

commented Jul 4, 2019

Use Case

A user is performing edits on an entity and its relations through a series of ajax requests. When they're done we want to send an email notification communicating the changes. We won't know if the user is done in any single request, but when the requests stop coming in. Ideally, we'd have some mechanism in place to Send email in 5 minutes that if another ajax request comes in making changes, we're able to push the queue job out another 5 minutes to make time for any additional changes.

Ideal Solution

Ideally there's a way we could query redis to determine if the job is already there and if so, perform an update on the amount of time it's delayed.

@mfn

This comment has been minimized.

Copy link

commented Jul 4, 2019

Ideal Solution

I'm not sure that solution is really ideal. There are other queue drivers besides redis and it may not be possible to do that kind of thing.

Without much experience in this particular area, I would imagine the best "aggregated job to delay" is the one which does not (yet) exist.

  • I.e. defer the logic to create such a job
    or
  • re-check the appropriate entities when executing the job to determine if sending the email is ok (but I'm sure that approach has too many not-easy solvable edge cases)

Just my 2c

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.