Skip to main content

Computing as a commodity

There is a key concept that links Utility Computing, Grid, Service-Oriented Architecture, Virtualisation and several more slippery terms as well. That concept is of computing as a commodity. This is not the same as computers being a commodity - we're all used to that, whether we're buying a home PC by mail order or building even mid-range servers from similar machines. Commodity computing lets us use computing resources or services when we need them and only when we need them. It takes several forms.

The most obvious example is Utility Computing, where a vendor (such as Sun or Amazon) provide you with CPU cycles or storage space and you pay for what you use. Web hosting companies operate on a similar basis, just slightly higher up the software stack. But other examples show that the same basic idea can operate within a company.

Trader Media are a classic example of how computing can be a virtual commodity within a company. They started with the classic setup of separate servers for web, database, business logic & development for each web product, with a complete set of duplicates for backup and failover. They now have a common set of servers with services deployed over them as necessary. Their server utilisation has risen from the industry average of 10% to about 50% and they are aiming for higher rates still. Larger industries can supply services to whichever departments need them, using internal accounting mechanisms much as in the inter-enterprise cases. So we can have a separation between servers and services.

Similarly, companies can provide services themselves as commodities. These can become parts of larger systems stretching across multiple companies. This is a small market as yet but there are enough examples out there to prove the concept.

All these scenarios are underpinned by common technological ideas. So although one term may become unfashionable and another take its place, or while one vendor's system may lose favour and another become more popular, we can see that the key concept that links them all remains the same. Computing is becoming a commodity.

Comments

Popular posts from this blog

Presentation: Putting IT all together

This is a presentation I gave to an audience of University staff: 

In this seminar, I invite you to consider what the University’s online services would be like, if we worked together to design them from the perspective of the student or member of staff who will use them, instead of designing them around the organisational units that provide them. I’ll start with how the services might appear to that student or member of staff, then work back from there to show what this implies for how we work, how we manage our data, and how we integrate our IT systems. It might even lead to changes in our organisational structure.

Our online services make a vital and valued contribution to the work of our students and staff. I argue that with better integration, more consistent user interfaces, and shared data, this contribution could be significantly enhanced.

This practice is called “Enterprise Architecture”. I’ll describe how it consults multiple organisational units and defines a framework …

Not so simple...

A common approach to explaining the benefits of Enterprise Architecture is to draw two diagrams: one that shows a complicated mess of interconnections, and one that shows a nicely layered set of blocks. Something like this one, which came from some consultants:


I've never felt entirely happy with this approach.  Yes, we do want to remove as much of the needless complexity and ad-hoc design that litters the existing architecture.  Yes, we do want to simplify the architecture and make it more consistent and intelligible.  But the simplicity of the block diagram shown here is unobtainable in the vast majority of real enterprises.  We have a mixture of in-house development and different third-party systems, some hosted in-house, some on cloud infrastructure and some accessed as software-as-a-service.  For all the talk of standards, vendors use different authentication systems, different integration systems, and different user interfaces.

So the simple block diagram is, basically, a l…

2016 has been a good year

So much has happened over the last year with our Enterprise Architecture practice that it's hard to write a succinct summary.  For my day-to-day experience as enterprise architect, the biggest change is that I now have a team to work with.  This time last year, I was in the middle of a 12-month secondment to create the EA practice, working mainly on my own.  Now my post has been made permanent and I have recruited two members of staff to help meet the University's architectural needs.

I have spent a lot of the year meeting people, listening to their concerns and explaining how architecture can help them.  This communication remains vital, the absolute core of what we do and we will continue to meet people in this way.  We also talk to people in other Universities in order to learn from what they are doing and to share our own experience back.  A highlight in this regard was my trip to the USA last January.

Our biggest deliverable for the past year was the design of the data wa…