Since this was on the front page, I took the time to figure out what IronWorker was all about. It looks to be cron, and memcached as a service, which to me are not real pain points. Twilio on the other hand is Asterisk, TTS, telephony gateways, and a bunch of other telephony stuff as a service, which is a real pain point. If I were to implement this app with neither iron.io nor twilio, it would be easy, however using…
It took me a while to understand the benefit of IronWorker however a 'server-less' environment is exactly what we need for some small discrete jobs. I know that these jobs will scale up (in number) without the need to deploy more servers or maintain them.
This is pretty much spot on as to IronWorker's sweet spot. Discrete jobs, no servers, never worry about scaling.