Fordism and the Cloud

In a recent Article Dustin Owens (2010) argues that elasticity defines the benefit of Cloud Computing.  He states “Elasticity could bring to the IT infrastructure what Henry Ford brought to the automotive industry with assembly lines and mass production: affordability and substantial improvements on time to market.” (p48). The article is useful and focuses primarily on security however it was the comparison with Henry Ford which got me thinking.

It is a bold statement and deserves further analysis. In particular it is unclear what Ford brought the motor industry – certainly increased penetration, increased usage, increased availability all of which are positive. Arguably though it also brought with it urban sprawl, oil-dependence, reduced wages and Tailorism. One can imagine similar problems with the cloud. Urban sprawl might be similar to flattening organisational sizes and increasing risk. For those companies whose data-centre provides competitive advantage will see an increased landscape of small competitors capitalising on the Cloud to compete – the sprawl. Our oil-dependence will similarly remain – Cloud computing hides the electricity and environmental impact of our actions in data-centres hidden from view. Purchases are unlikely to know what percentage of costs are electricity – and are unlikely to care. Finally reduced wages and Tailorism. Prior to Ford those involved in developing cars were highly skilled and worked across the line – Ford reduced this movement of skill, and Fredrick Tailor developed this into scientific management. One can see similarities in the cloud provider with increased specialism among staff  within these very large data-centres. With this comes risks – the generalist is better able to respond to radical architectural change and innovation. The generalist also has a more interesting job (a failure of Scientific Management). All this is speculation at the moment – I await my first Model T Cloud.

On another level however this comparison is interesting. because it is worth remembering that Ford was overtaken by General Motors for the simple reason that Henry Ford was against debt and demanded people pay in cash, whereas GE realised that borrowing to buy a GE car was beneficial. With the car you’re earning potential rose as you could travel for work and you were thus better able to afford the car.

In cloud computing the same might also be true. The argument behind Cloud Computing has always been that start-up ventures do not need to purchase the expensive IT equipment they can focus on  Opex not CapEx. Similarly SaaS offers reduced CapEx costs. But one might also imagine a growth of financial services industries around the cloud. For example providing short-term loans to allow small companies to ramp up websites in response to incredible demand (and perhaps insuring against this). Or allowing small media enterprises to rent cycles for rendering films as a percentage of future profits. Finally, and perhaps most importantly, if computing is a commodity we are likely to see spot-markets and commodity markets spawn. Can we imagine CDOs developing based not on sub-prime mortgages but on poorly used processor cycles within the cloud… or imagine insuring against a Denial of Service Attack such that when one occurs you can ramp up website services to respond, but not have to pay for the processor cycles! I can see many small companies taking out such insurance for their websites (if anyone profits from this – then donations received with thanks 🙂 ).

——

Owens, D (2010) “Securing Elasticity in the Cloud”, Communications of the ACM 53(6) 48-51 doi:http://doi.acm.org/10.1145/1743546.1743565

Green Computing and the Cloud – SETI@home

Cloud computing hides the environmental impact of computing from the user. When we search using Google our own PC doesn’t suddenly start to cough – the fan doesn’t ramp up, our laptop doesn’t burn through the table. But somewhere in Google processors are using energy to undertake the search. Google is aware of this and tries hard to reduce this cost and its environmental impact.

There is a corollary of this though. When we use peer-to-peer software our processor uses more power and more electricity but we seldom notice. While perhaps tiny in aggregate this can be significant. And unlike Google few of us think about it, or try to use renewable energy to reduce its CO2 emissions.

Let me demonstrate with a quick back-of-the-envelope calculation.

SETI@home (the peer-to-peer application searching for ET) has 5.2 million participants and has produced an aggregate two million years of computing time. Taking an example of power usage for basic computers we can see that the difference between an idle computer and a in-use computer (i.e. where SETI is doing its processing) would be around 20watts ( though perhaps more). Given SETI has run for 17,520,000,000 hours that works out at about 350,400 Megawatt hours or 350.4 Gigawatt hours.

The UK average consumption of Gas and Electricity is about 22,338kWh per household (in 2007).  In the ten years since it started SETI@home has used about as much energy as a town of about 15,000 people would use in Gas and Electricity in an entire year!

Interestingly assuming US consumer energy costs (since most will be in homes in the US) at about 8c per kw/h this is about $28million of electricity! The key points is that this is only about 50c per year per participant – scarcely enough to make them change their SETI screensaver, but highly significant in the aggregate.

And SETI@home has yet to discover anything alien!