Skip to main content

"That's not Grid!" - A cautionary tale

I don't usually attempt humour here, but see if you like this...

Once upon a time, in the far-off world of Computerland, a great guru arose and declared a vision.

"I see a future when all computers will be linked together and people will run their programs without knowing which computers are running them. People do not need to know where their jobs run; they just need the results. I call this Grid Computing!"

The people of Computerland were excited by the guru's vision. They went away and worked to make it happen. When they were ready, they returned to the guru and said:

"Oh great guru! We have implemented your vision. We can run our programs on whichever processor is free at the time, making sure that all programs can run and making best use of all our processors. No longer does one computer sit idle while another one is overloaded. Your vision is a great success!"

"No, no, no!", said the guru, "That's not Grid!"

The guru explained, "What you have implemented is just cluster computing. Grid computing is about linking machines that are administered separately".

The people of Computerland were excited by the guru's vision. They went away and worked to make it happen. When they were ready, they returned to the guru and said:

"Oh great guru! We have implemented your vision. We can run our jobs on all the desktop PC's of the world. We have run the biggest climate model ever and we have used it to find new drugs against deadly diseases. Your vision is a great success!"

"No, no, no!", said the guru, "That's not Grid!"

The guru explained, "What you have implemented is just cycle-stealing. Grid computing is about making computing power available on demand; a utility similar to water or electricity. It's not just about using spare capacity".

The people of Computerland were excited by the guru's vision. They went away and worked to make it happen. When they were ready, they returned to the guru and said:

"Oh great guru! We have implemented your vision. People can buy processor time and disk space when they need it. Our computer resources are available to anyone who can pay. Your vision is a great success!"

"No, no, no!", said the guru, "That's not Grid!"

The guru explained, "What you have implemented is just utility computing. Grid computing is about linking many distributed resources to address a single problem".

The people of Computerland were excited by the guru's vision. They went away and worked to make it happen. When they were ready, they returned to the guru and said:

"Oh great guru! We have implemented your vision. People provide their programs as services using standard protocols. Then users can combine these services in new and unforeseen ways using scripts or workflows. Our businesses are more efficient and agile. Our scientists have made new discoveries. Your vision is a great success!"

"No, no, no!", said the guru, "That's not Grid!"

The guru explained, "What you have implemented is just service-oriented architecture. Grid computing is about common information and management protocols so distributed resources can be tightly co-ordinated".

"Oh!", said the people, "But we have already revolutionised our business methods, increased our agility and resource utilisation, put our previously wasted computer power to good use, provided computer power to people who need it, produced new science and found new ways of working together. We don't need anything more".

With that, the people stopped the guru's research grant and forced him into a life of giving keynote speeches on the conference circuit.

Moral: Don't define yourself out of success.

(Disclaimer: Given the opportunities for misunderstanding on the internet, I feel I have to stress that this is not aimed at any particular individuals).

Comments

Ravi said…
Thats very subtle..I especially like the disclaimer you had at the end of the article.. I had a fleeting suspicion who it was but not after reading the disclaimer. Good work Dave.
Dan Ciruli said…
subscribed!
Dick said…
brilliant!

Popular posts from this blog

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

Why the UCISA Capability Model is useful

What do Universities do?

This may seem a strange question to ask and the answer may seem obvious.  Universities educate students and undertake research.  And perhaps they work with industrial partners and create spin-off companies of their worn.  And they may work with local communities, and affiliation bodies for certain degress, and they definitely report on their activities to government bodies such as HEFCE.  They provide student services and support.  The longeryou think about it, the more things you can think of that a University does.

In business, the things that an organisation does are called "capabilities", which is a slightly strange term.  I think it is linked to the HR idea of a combination of the CAPacity and ABILITY to do a task.  Whatever the name, it is a useful concept.  A capability is more basic than a process: a University may change the way it educates students but as long as it remains a University it will educate them one way or another.

A capability …

A new EA Repository

One of my goals since starting this job two years ago has always been to create a repository for architecture documents.  The idea is to have a central store where people can find information about the University's applications, data sources, business processes, and other architectural information.  This store will make it easier for us to explain our plans, to show the current state of the University's information systems, and to explain what Enterprise Architecture is all about.

It's taken a long time to reach this goal, mainly because we're often had more pressing and immediate work to be done.  The creation of a repository is one of those tasks that is very important but never quite urgent.  So I'm now very happy to say that we are in the process of deploying a repository and modelling tool.


This is the culmination of a careful process to select the most appropriate tool for our needs.  We began by organising several workshops to gather requirements from a rang…