IronMQ push queue subscribers as Heroku workers -


ironmq supports push queues, example heroku push queue subscriber implemented web dyno. feels awkward, because need single heroku project use web dynos serve web requests, , worker dynos process time-consuming needs. that's how heroku designed.

the ironmq api indicates push queue subscriber should accessible via publicly-accessible url; that's why web dynos necessary.

is there (clean) way ironmq push queues publishers , subscribers within single heroku project?

is there queue service support (even long-polling subscribers work)?

if wanted use ironmq non-web-accessible server, best advice use pull queues. start worker dyno, , have pull down messages available every x seconds. 10 million requests free, you're using 26% of free quota if check messages every second.

if still wanted push queues , had tcp port listening on worker dyno, use push queues , have each message start worker on ironworker translates message tcp connection instead of http connection.

hope helps!


Comments

Popular posts from this blog

c - How to retrieve a variable from the Apache configuration inside the module? -

c# - Constructor arguments cannot be passed for interface mocks -

python - malformed header from script index.py Bad header -