On Tue, May 21, 2013 at 12:37 AM, Jesús Gabriel y Galán <[email protected]> wrote: > So I made a proof > of concept in which when a user subscribed I insert a job in > beanstalkd with a week delay. Then n workers will listen for jobs, get > one, make a try and if it fails return it to the queue with a > calculated delay (5 minutes or 1 day, for example).
It's hard to say whether this is good without knowing some more details about what you're doing. But if you've already tried it and it works well, then I'd say it's a good approach. > should I use an external database and run checks against this > external data That will probably be more reliable in the long run. Beanstalkd isn't a database. You might consider a periodic cron job that scans the database looking at timestamps, and generates beanstalkd jobs to do whatever work is necessary. But again, evaluating these approaches is hard to do in the abstract. -- You received this message because you are subscribed to the Google Groups "beanstalk-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/beanstalk-talk?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
