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

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…

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…

A brief summary of our major initiatives

I notice that in 2016 I wrote 34 posts on this blog.  This is only my fifth post in 2017 and we're already three-quarters of the way through the year.  Either I've suddenly got lazier, or else I've had less time to spend writing here.  As I'm not inclined to think of myself as especially lazy, I'm plumping for the latter explanation.

There really is a lot going on.  The University has several major initiatives under way, many of which need input from the Enterprise Architecture section.

The Service Excellence programme is overhauling (the buzzword is "transforming") our administrative processes for HR, Finance, and Student Administration.  Linked to this is a programme to procure an integrated ERP system to replace the adminstrative IT systems. 

Enabling Digital Transformation is a programme to put the middleware and architecture in place so that we can make our processes "digital first".  We're implementing an API framework, a notification…