I seemed to have caused some heat a few days ago when I suggested the future of corporate IT was “everything for nothing”. My point was that commoditisation of technology inputs would reduce their price to a point where they would, effectively, be “too cheap to meter”.
Since then, many people have written to me privately saying they “don’t get” the argument I’m making, though most have been polite enough to stop short of telling me I’m wrong.
So I thought I’d better explain myself a bit better, perhaps with the aid of some of the public comments on this blog.
Let me start with the basic refutation of free from Anon, who reduces the argument to economics:
…until food, clothing and shelter are free how people who make the free stuff for others to consume can make a living. Nothing is free to make for others to use. The Internet is not 100% free as someone needs to be paid to keep it up and running and they use this payment to buy food, clothing and shelter.
OK, so I admit at this point some dramatic licence when describing the price as “nothing”. Quite clearly, someone is going to pay for stuff, particularly the stuff that uses atoms. Perhaps I’d have been better off using the “too cheap to meter” phrase instead.
Now this is a world we’re already in. I buy an internet connection today, and pay about ten pounds a month. Every year or two, the width of my pipe has doubled without much in the way of a price increase. The trend is obvious, and is the same for the computers I’m using, and everything else in my life that depends on IT. My bandwidth, anyway, is too cheap to meter. So is all the rest of the technology around me.
I mean, there is a CPU in my light switch now. It knows how to do the dimming and switch-on things when I point a remote at it. Those are cycles that are too cheap to meter.
But Thomas Barker, regular commenter here says this:
Focusing on CPU cycles is a red herring. They aren't the bottle-neck in business systems. Most systems spend all their time on I/O, so if anything, you'd expect massive consolidation *within* datacentres to economise on disk activity and storage. Not processing being dynamically relocated across continents. The bandwidth to push the data around is more expensive. CPUs are cheap.
Now, this may be true today. But the inexorable price decline in bandwidth on public networks is irrefutable. Its easy to see when bandwidth will be cheaper than cycles.
Anyway, Thomas has missed the point, I think, when it comes to cycles. Its not the chips which are going to be expensive, its the power. There is going to be an energy shock sooner or later, just like the oil shock on 1973. That had the result of hugely inflating the price of crude, with the result that everyone suddenly had to be concerned about fuel efficiency.
It is not hard to imagine a carbon tax on datacentres in the next decade. What would that do to the price of your processing?
Most countries are inefficient producers of cycles. When you can’t get enough power into your datacentre no matter what you do, you’re going to be forced into running your workloads virtually elsewhere. I’ll not make any predictions about storage, except to say that if you have virtual workloads moving around, I’d expect the storage to move with it. Thomas correctly identifies that having the data with the workload is usually a good thing.
But on to the desktop. Internally, I got an email from someone that reminded me that “the cost of a desktop isn’t the hardware, its the support to make it all go”. I paraphrase, but the point, really, was that bodies have to sit around to fix things that stop working.
The fact of that matter, though, is that there is a growing population of people in enterprises who are able to fix things themselves, and who, actually, have better skills at doing so than the corporate helpdesk. When you let them get on with managing their own tools, they’ll be much more productive that that big lumbering corporate helpdesk would have let them be.
That’s not everyone, today. But it is a growing body of people, and sooner or later, its going to be a majority.
I want to close with another point from Thomas’s comment:
As for people hacking their own business programs, it can help, it is how most useful things start, but scaling, or integrating, stuff like that... eeek!
I know you all know my argument here is going to be obvious: Open Source does all of these things perfectly well. Software that evolves from the bottom up works, even in a business context. Having your end users do it rather than coders is a question of waiting for the right tools, not any lack of motivation or capability.
I cannot imagine that end-user computing tools a decade from now won’t routinely be capable of doing big systems.
I have one final point to make. Most of the communication I got on this post came from IT professionals, all of whom said that none of this could happen for various reasons. The discussion I got from non-IT colleagues, though, was along the lines of “but isn’t this obvious?”
What conclusions would you draw from that? Here are mine: big IT will be over in the next decade or so, and all those professionals who manage the commodity inputs had better get themselves up the foodchain quick smart. Those that fail to recognise that they’re not that special any more will be out.
And if you sell the commodity inputs, be prepared for your nice premiums to crash. Our needs aren’t so special that you can charge us over the odds. You too, will be out unless you can dream up something that makes you special again.