Blog

Search This Blog

Loading...

Thursday, April 25, 2013

Iron.io Joins OpenStack to Drive Open Cloud Message Queues


Iron.io is now an OpenStack supporter. This may not appear all that unusual – given the top companies originally behind the initiative plus the growing numbers joining – but it is noteworthy for a cloud services company. 

With most cloud services, it shouldn’t really matter what the underlying IT stack or even what cloud you’re running on. API-driven services essentially abstract the VMs, infrastructure, and scaling away to provide elastic utility-based computing. Just plug into the APIs and eliminate the need to provision resources based on current or anticipated loads. 

Wednesday, April 17, 2013

IronMQ 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. That means we are executing your code across our farm of worker servers, half a million times per day.

Thursday, April 11, 2013

Relify 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 details their use of a scale-out processing pattern that, in concert with IronWorker, allowed them to significantly scale their recommendations service. All in a short period of time without any infrastructure or much cost.

Tuesday, April 9, 2013

IronWorker API Outages - Post Mortem


Starting around 9:45 PT on April 6th, the IronWorker API started having issues where requests to the API would not receive a response and timeout. The issues were intermittent over the next few days with short outages followed by hours of normal operation. The cause of the issues were a couple infrequently used queries that weren’t using indexes, more information on that below. The issue was finally resolved around 2:45 PT on April 8th.

Note: this only affected the IronWorker API. IronMQ, IronCache, the IronWorker scheduler, and the IronWorker backend were not affected.

Thursday, April 4, 2013

Iron.io @ New York Hackathons (Hack Upstate and UB Hacking)

Iron.io is excited to be a sponsor at two upcoming hackathons in New York. Both are in upstate New York is showing lots of cool tech activity lately. This is great for us because it gives us an opportunity to connect with some awesome projects, teams, schools, and organizations.

Hack Upstate

Hack Upstate is a weekend hackathon where developers, innovators and designers from Upstate New York will come together in Syracuse, NY, share ideas, form teams, and build awesome products. 
The goal is to unite and facilitate collaboration among the greater Upstate New York hacker community. In doing so, Hack Upstate aims to contribute to the growth of Upstate New York's technology sector, and to create a robust network of technologists and regional technology companies. 

UB Hacking


April 13th-14th
UB Hacking is a 24-hour hackathon hosted at SUNY Buffalo by the UB ACM. It is a hackathon for students by students designed to see awesome ideas brought to reality. UB Hacking will provide meals for the entirety of the hackathon, a place to nap (yeah, right), awesome free swag, prize money, and more!

Iron.io for Speed, Scale, and Simplicity

When you have 24 hours to create an application that does something powerful or just fun, you need simple powerful compute services. Iron.io provides three core services that let you quickly build applications that do big things.

  • IronMQ is the message queue for the cloud, allowing developers easily facilitate asynchronicity, load buffering, work dispatch, database offloading, and more. 
  • IronWorker is a massively scalable task queue for background processing, job scheduling, and map-reduce-like scale-out processing.
  • IronCache is a durable and elastic key-value data store for storing counters and global state data, temporary data values, or the results of processing.

We should note, the same benefits around speed, scale, and simplicity also apply when it comes to developing production-scale mission critical applications. Development speed always wins, even more so when combined with scale and reliability.

Iron.io on Hand

Paddy Foran, a developer experience engineer at Iron.io, will be on hand at both events. He can help with thinking up project ideas as well as assist with making use of Iron.io's simplicity and scale to help bring home some loot. (Iron.io will be giving out some Raspberry Pi's and Arduino boards to the top teams using Iron.io.)