On Jun 18, 6:22 am, Jonathon McKitrick 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 constant
As you suspect, the Heroku cron job launches, executes code, and bills you
for its time and the 'worker' process, like the 'web' process, runs at all
times.
web:lein run -m myapp.web
worker: lein run -m myapp.worker
I imagine myapp.worker can just be (while true (println "Working")) for all
You are correct, I meant to say 'worker process type' as opposed to 'web
process type'.
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 jo
Heroku cron jobs and workers are prorated like dynos. They run in their own
processes. So does booting into heroku bash or heroku console.
Workers generally consume a queue.
I'm not sure what you mean by "worker thread" though. Workers don't run in
a thread, and you can launch plain old threads
How would you sum up the differences? Does the worker thread simply run
all the time? Wouldn't that run up the dyno usage?
--
--
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 p
