Skip to main content

Garbled Grid Hype

There has been some rather confused coverage in the press about the grid infrastructure that supports the Large Hadron Collider at CERN. The Times has an article that cast the grid as a "superfast internet", with the emphasis on the high-bandwidth links that have been laid to support the LHC data dispersal. It also talks about the numbers of servers connected to the LHC grid, but without clarifying the distinction between bandwidth and processing power. It also implies that the LHC grid is the only grid, which perhaps we can forgive the journalists for, as plenty of technical people still refer to "the grid" as if there were only one.

A Yahoo article, taken from Sky News, goes rather further, claiming that "the internet, as we know it, could be obsolete within a decade". The phrase, "as we know it", lends a wonderful vagueness to the claim. The article goes on to say that the Grid was the brainchild of CERN, which of course is an exaggeration. On the technical side, this article is possibly better, describing the LHC grid as a linked network of computers and describing some of the applications that it has been used for. There's just one paragraph where the illustration of bandwidth has been taken rather literally and expounded as if every household will have such connectivity, which is a separate issue.

I'm sure that none of the inaccuracies are the fault of the people mentioned in the articles. Journalists need to tell a story snappily and with an "angle" that will interest their audience. But the grid community need to do a better job of telling people what grids are about. We are doing our bit by producing some new material for Grid Computing Now!, which should be on the web site shortly.

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…