Here are a few updated differences. disclosure I work for Iron.io Lambda: node, java IronWorker: node, ruby, python, php, java, binaries, .NET, go (binaries),

Here are a few updated differences. disclosure I work for Iron.io Lambda: node, java IronWorker: node, ruby, python, php, java, binaries, .NET, go (binaries), and more (specific language runtime versions available) Lambda: allows 500mb of local disk space to persist your task IronWorker: 10 gb of local disk space available Lambda: only current version of code IronWorker: versions all uploads and allows you to revert Lambda: no built in scheduler IronWorker: a flexible scheduler out of the box to run tasks Lambda: maximum execution time 60 seconds IronWorker:maximum execution time 1 hour (customizable up to 24 hours for dedicated users) Lambda: 100 maximum concurrent request. (The maximum can be higher, can someone point me to the absolute maximum if it exist?) IronWorker: concurrency maximum can go much higher as needed (250 for a production plan). You can also limit concurrency per IronWorker, aka set a worker to only run up to 50 concurrent tasks. (useful if you have bottlenecks) Lambda: 90 inactive code retention period IronWorker: no limit to inactive code retention period Lambda: available on aws IronWorker: choose your cloud provider: AWS, Rackspace, Microsoft Azure, private clouds, and more. We've also enabled users to pause the execution of their task queue incase they need to patch or revise their worker code. supporting your own docker images http://blog.iron.io/2015/06/no-lock-in-thanks-to-docker.html http://blog.iron.io/2015/06/no-lock-in-thanks-to-docker.html http://blog.iron.io/2015/05/full-docker-support-for-ironworker.html http://blog.iron.io/2015/05/full-docker-support-for-ironwork... We’ve been doing some very neat stuff with our local docker development workflow https://medium.com/@treeder/why-and-how-to-use-docker-for-development-a156c1de3b24 https://medium.com/@treeder/why-and-how-to-use-docker-for-de... edits* formatting Overall we are are glad Lambda is validating workflows around eventable compute services. It's an experience we've been innovating for some time now.