We used Iron.io as a one stop shop to help us get onto the cloud and tune our services to get cloud efficiencies. It was overwhelming looking at the many disparate services that need to have the dots connected to get underway with the cloud, so giving this problem to Iron made things much easier as we had a single touch point. Iron's Worker is a complex tool and is hard to understand how to engage it effectively in your architecture - it essentially changes your serial processing pipeline and multiplies them to enable parallel processing - effectively unblocking bottlenecks and seeing less cloud compute needed to get results in a certain time frame. The result has been a drastic reduction in the AWS spend we have been getting, as we are finally optimized to take advantage of the elasticity that cloud computing offers.

We love the push queues on Iron MQ. Queues are easy to setup and manage in different zones to best suit required availability.

- I improved my CSV breakdown work drastically by putting 10 Iron Workers on the job. Up to that point, I was just using larger AWS instances... But the concept of actually running 'concurrent' jobs at the same time (through using workers that spin up on elastic cloud computing) was lost on me. - The UI is very intuitive and gives really good detail about the time each job takes. - I can run my Workers and then have them put the finished product on a message queue - which means my whole ETL process is done without any hassle.