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

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…