Aggregated Queue Job - Event changes delay the event further so it only fires once #1705
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
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.
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.
Just my 2c