[dchesterton]

We're using IronWorker and Lambda for a current project. Our (Go) code can run on either and we've designed the app to easily swap out the backend in case of service failure.

Pros of IronWorker: More language support, better logging, easier to debug, scheduled tasks via API (this is the main thing stopping us going all in on Lambda).

Cons: Slower start up time (~2-3s on average compared to milliseconds with Lambda), pay upfront rather than pay for what you use, no choice re. CPU/RAM.

[carimura]

Thanks for the synopsis. Lots of plans for IronWorker including fully custom Docker image support (soon) and millisecond response times (soon'ish). We also support custom configurations of CPU/RAM for dedicated customers which is what most of our customers with stricter SLA's utilize.

That said, a big differentiator is IronWorker's ability to be deployed to any cloud provider as well as private clouds / on-premises. Many of our enterprise customers need hybrid deployments.

We're always listening so please feel free to shoot us feedback at support[at]iron.io or find us at @getiron.

Chad @ Iron.io

[vosper]

You may be interested to know that Lambda now supports scheduling: https://aws.amazon.com/blogs/aws/aws-lambda-update-python-vp...

Edit: Oh, are you saying that you want to send an API call to schedule something? They say in the post that API support is coming, but I don't know if you could schedule a one-off run that way.

[dchesterton]

Yeah, we connect with other services so we need the ability to programmatically re-schedule a function to run in ~5 minutes if it failed the first time.