On Jun 18, 6:22 am, Jonathon McKitrick <jmckitr...@gmail.com> wrote: > So, the question then, is what would be the difference between a heroku > scheduled command (which I currently am running, wakes up, does some work, > etc) and a 'worker process' type? Does the latter need a job queue set up? > Does it run constantly, checking that queue and consuming work items from > it?
The reply from danneu is right; but more specifically you should set up a worker process type if you've got enough work to keep a process busy full-time or if you need a quicker turnaround time for the work you're sending it. A scheduled process will be cheaper in terms of time consumed, so if you're not currently bothered by its limitations you should probably stick with it. Either a worker or a scheduled process can use a queue to get its jobs, or it can get it from a DB if the volume is low. -Phil -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
