Posts Tagged ‘IronWorker’
Map-Reduce Capabilities and Super Easy Concurrency (via Alan deLevie and IronResponse)
We came across a great contribution the other day from Alan deLevie that makes using IronWorker for a map-reduce pattern even easier than it already is. (Love seeing tweets announcing additions to the growing list of Iron.io community addons.) I just wrote a gem that lets you write map-reduce style code using @getiron: https://t.co/49DNyLrXey. Makes…
Read MoreReal-time Logging for IronWorker
Overview One of the most common feature requests we get for IronWorker is the ability to view logs in real-time while your workers are running. Until now, you had to wait for your IronWorker tasks to finish before being able to view the log and it can be pretty frustrating to try to debug your workers…
Read MoreIron.io Announces Agent Processing for Powering New Relic Plugins
Today Iron.io announces powerful agent processing capabilities for powering third-party plugins for the New Relic Platform. New Relic has opened up its SaaS service to provide building blocks for creating monitoring capabilities for any technology or service. Performance metrics from IT components and cloud services can now be brought directly into New Relic and viewed…
Read MoreIronMQ Handling 250M Requests Per Day, IronWorker Executing Over 500K Jobs
This month, Iron.io hit two major milestones in our usage numbers for two of our services. IronMQ is now handling over 250 million requests per day (== 174K per minute == 2,900 per second). This is up from 100 million just three months ago. Also, IronWorker is now executing over 500,000 jobs (tasks) per day.…
Read MoreRelify adds IronWorker to their Stack ➞ Ridiculously Simple Worker Scalability
Relify, a Recommendations as a Service engine, is one of the really cool customers that Iron.io serves. They offer a simple API that eliminates the complexity of developing a recommendation engine –which means you can greatly increase your relevance to your users. Terry Horner is the Co-Founder and CEO of Relify. A recent blog post of his…
Read MoreHow We Went from 30 Servers to 2: Go
When we built the first version of IronWorker, about 3 years ago, it was written in Ruby and the API was built on Rails. It didn’t take long for us to start getting some pretty heavy load and we quickly reached the limits of our Ruby setup. Long story short, we switched to Go. For…
Read MoreIron.io + OpenShift : PaaS 2.0 for the Enterprise
Iron.io is pleased to announce we are now a developer partner on OpenShift. OpenShift is Red Hat’s auto-scaling Platform as a Service (PaaS). Red Hat has a rich history when it comes to technology and large IT systems and, with OpenShift, they’re on a serious path to make history happen again, this time in the…
Read MoreSharable, Open Source Workers for Scalable Processing
Overview You can now add workers to your account from a GitHub URL which enables an awesome way for people to share their workers with others. In this post, I’ll show you three real-world examples workers that you can start using right away without writing a line of worker code. The power of any worker…
Read MoreNew Feature: Auto Retry for IronWorker
Overview IronWorker now has an auto-retry feature that, if enabled, will automatically retry your tasks if they error out. You can set the number of times it should retry and the delay between retries. Usage While uploading your worker, simply set the retries and retries-delay parameters: iron_worker upload my_worker –retries 5 –retries-delay 10 That example…
Read MoreWeb Crawling at Scale with Nokogiri and IronWorker (Part 2)
This is the second part of a two-part post on using IronWorker with Nokogiri to do web crawling at scale. The first blog post can be viewed here. Other resources for web crawling can be seen on our solutions page as well as this post on using IronWorker with PhantomJS.
Read More