4 ms·
The IronWorker doesn't seem to fulfill the same promise of simplicity that Lambda does. It's talking about scheduling and creating docker instances where Lambd
by stuartaxelowen 11y ago
The IronWorker doesn't seem to fulfill the same promise of simplicity that Lambda does. It's talking about scheduling and creating docker instances where Lambda says "just give us your code".
- treeder 11y agoDocker support is a new feature to enable more complex jobs where you need to control the entire stack, for instance, maybe you need imagemagick installed on the core machine, or ghostscript. IronWorker can support that. It also allows you to test your workers locally before uploading: http://blog.iron.io/2015/03/the-new-ironworker-development-workflow.html http://blog.iron.io/2015/03/the-new-ironworker-development-w.... That said, you don't need to think about Docker if you don't want to and an IronWorker can be a few lines of code too, for example: https://github.com/iron-io/dockerworker/blob/master/ruby/hello.rb https://github.com/iron-io/dockerworker/blob/master/ruby/hel... Or node: https://github.com/iron-io/dockerworker/blob/master/node/hello.js https://github.com/iron-io/dockerworker/blob/master/node/hel...
- stuartaxelowen 11y agoThanks for posting those, their splash page gave me the feeling that you were always responsible for the docker mental overhead.