|Docker Solved a Key Problem
Ever since we started Iron.io, we’ve been trying to solve a problem: how to keep our IronWorker containers up to date with newer language runtimes and Linux packages. For the past two years, IronWorker has been using the same, unchanged run-time environment. That is until a couple of weeks ago when we released custom language environments.
Since the inception of our service, we have been using a single container that contained a set of language environments and binary packages – Ruby, Python, PHP, Java, .NET, and the other languages we support as well as code libraries such as ImageMagick, SoX, and others. Continue reading “How Docker Helped Us Achieve the (Near) Impossible”
Here in San Francisco hackathons are common place — you can find one most every weekend.The basic premise of a hackathon is to show up, build an app in 24-48 hours, and go home. All food and drink is taken care of and sleep is frowned upon, though a couple hours of nap time is suggested. The draw of hackathons, other than the lack of sleep and free food, are the prizes you can win which range anywhere from a few hundred dollars to a million. Continue reading “Hackathons: Beyond the Prizes”
IronSharp is a great new contribution from a long-time supporter and user of IronMQ, IronWorker, and IronCache.
Jeremy Bell created IronSharp to provide updated access in .NET to all Iron.io services. It’s a simple solid library that wraps the API calls for IronMQ, IronWorker, and IronCache and includes support for the latest Iron.io features. (It also has a great logo and GitHub page.) Continue reading “IronSharp — .NET Client Library for Iron.io (a contribution from a user)”
After running Go for two years in production at Iron.io, I wanted to share our experience/feelings about it. We were one of the first companies to use Go (golang) in production and we didn’t know what to expect in the long run, but so far, so great.
I talked a little about about this in a previous post about switching to Go from Ruby, but this will go into specific things that we love about the language, the things we learned along the way. In no specific order, here they are:
Continue reading “Go After 2 Years in Production”
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 the long story, keep reading, here’s how things went down.
Continue reading “How We Went from 30 Servers to 2: Go”
We received a nice writeup in the API Evangelist blog the other day. (If you don’t follow Kin’s writing, you should. He’s on top of his game when it comes to API technologies and API-driven business models.) The post talks about everyone in API-driven companies being a developer evangelist.
Continue reading “Ich bin ein Evangelist”
Platforms, Languages, and App Services
The case for cloud platforms is being made convincingly these days. Platforms magnify the power of virtualized cloud infrastructure first by providing an ability to quickly deploy and scale applications. And second by providing greater visibility and control of this virtual environment. The growth and success of platforms such as Heroku, AppFog, and others make it clear that this component of the cloud stack is not just central to building scalable apps but also key in terms of reaching and influencing developers.
Continue reading “Platforms, Languages, and App Services: Economies and Communities of Scale”