So you are storing a job in the database then - a job whose job it is to send a job to RabbitMQ/Redis :-)
Honestly I think that's the ideal way of doing things, however that's not often how you see it done.
Honestly I think that's the ideal way of doing things, however that's not often how you see it done.
Also, take a look at #5 for a great monitoring stats solution.
You must be storing enough representation of the job to re-send it though, no? You couldn't do this with a simple flag for all job types I imagine.
> in most cases it's just the absence of the desired effect that can be a giveaway
Sure, but not all jobs create side effects you can easily look for (e.g. sending an email). And secondly, you'd have to create a "sweeper" process for every type of job you create then.