IronWorker Reviews

Iron.io has revolutionized our business operations, streamlining our workflow. Their platform's integration capabilities seamlessly melded with our existing systems, delivering an unprecedented level of efficiency and reliability.

The standout feature of Iron.io undoubtedly lies in its unparalleled customer support. The team's responsiveness, depth of knowledge, and proactive approach to addressing our queries have been instrumental in ensuring a smooth user experience throughout our journey with them.

One area where Iron.io could enhance its offering is in providing more comprehensive documentation and tutorials. While the platform is powerful, navigating its full potential can be a bit challenging without extensive guidance. Improved documentation would significantly benefit users, especially those new to the platform, by streamlining the learning curve and maximizing its utility.

IronWorkers use Docker containers to deploy the workers and because of this, it is very easy to ensure consistency with your local environment

There hasn't been a ton of innovation in the product over the past few years, but not sure there needs to be

I used IronWorker for over 5 years and what separated them from the rest is the ease in deploying workers across a range of programming languages. I personally used them with PHP, Python, and Ruby workers and all worked well.

Iron Worker is an excellent solution for all requirements that my team need in your day work.

Each one of them say that this tool help keep an order in your process of design

For now is impossible to say that this product is bad because each day my team discover anything new to prove.

None

The queues are a very clear way to see where the processes are

Logs are not easily accessible, so it's hard to find a problem when something is not working.

File parsing and SMS queue Iron.

I love that IronWorker supports PHP. natively. Also, the scheduler is a great feature. Makes it easy to run PHP functions in the cloud without having to provision servers or containers.

There is no way to edit code in the dashboard. To update the code, even for a minor change, requires upload of the entire solution. This is generally not a problem.

Just do it. It's really great. Easy to use. And natively supports PHP!

We mainly use IronWorker for scheduling jobs which would otherwise require us to have a dedicated machine running CRON.

Ease of setup and use. The dashboard makes keeping track of various tasks and workers easy. Very little maintenance required once set up.

It would be great if there was a plan between Launch and Professional. That is a large gap, but one you have no choice to take if you need the extra horsepower.

We were able to use Iron.io to help us integrate robust queueing systems in conjunction with our API platform to increase the number of jobs we could process. Being able to set up a fail-over environment for these jobs has also been a plus. We can kind of "set it" and "forget it", and just let them run.

The MessageQueue is awesome, it is so fast and efficient! Their on-premise solution is perfect for our needs. Where compliance and security is paramount, the on-premise install is key. If we ever need assistance their support team has always been there and got us on track very quickly.

The cost can be a little difficult as there is no plan between the Launch and Pro. I would love to see a middle tier plan as the gap there is a little too large.

We have a new project requiring us to scale fast and Iron really helps us do that very efficiently.

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.

Iron.io's offerings are hard to understand from the outset, and they can probably make their language more accessible. Implementing their tools I feel would be a challenge without their help.

We searched for a way to simplify and reduce our AWS spend, plus optimize our computing processes. We didn't realize that we were just dumping more EC2 resources on problems that were effectively putting more muscle behind pushing a golf ball through a garden hose, when Iron's Worker allowed us to spit the golf ball into smaller balls and push them through multiple hoses... If that makes sense. But beyond this, we were also able to configure these smaller balls to look how they needed to look for the next stage of the process, and put them easily onto Iron's MQ. In effect, our benefits realized were reduced EC2 spend (40% drop) and a drastically simplified workflow (ETL to break down CSVs, reorganize the data and then load that data to multiple destinations at high speed).

- 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.

Iron's message queue did used to have downtime - but they have released a new MQ v 4 built on RUST that has been really great.

Ironworker is easy to use as well as easy to setup.very little maintenance required once setup. The scheduler is a great feature.Also the PHP functions is easy to run the cloud without having provision servers or containers.

There is no way to edit code in dashboard .It would be great if there was a plan between launch and professional.

We mainly use ironworker for scheduling jobs which would otherwise require us to have a dedicated machine running CRON.