Skip to main content

Storage meets the Grid

I'm just back from OGF19, which was very productive in a number of ways. One strand of interest is the continuing dialogue between the storage industry (represented by SNIA) and the grid world. This conversation has been developing slowly over the last year. I was on a panel at MSST 2006 that explored some aspects of this. SNIA were also present at GGF18 to explore where the two concerns meet. Both sides are still learning about each other, as they are both complex and changing technologies.

One obvious area of overlap is that of data replication. Many grid projects maintain replicas of data, to improve access times and/or to guard against loss. The classic example is the LHC Grid, but there are many other examples, particularly in the world of data librarines. Meanwhile, the storage industry supply replication systems for commerical data, specialising in backups and disaster recovery.

The two technologies work at different levels. Storage systems copy data from one disk block to another, with no knowledge about the data being copied. Grid systems copy files or database tables (in fact these two are themselves very different technologies), while maintaining application-specific metadata. Storage systems are usually deployed over LANs while grids are deployed over WANs, but this is not a hard and fast rule.

It remains to be seen which approach is best in which circumstances. Certainly there seem to be standards and tools from the storage industry that might be useful in the grid world, and vice versa. This will be an interesting conversation for some time.

Comments

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…

New staff for the EA team

I'm delighted to welcome Jason Murphy, who joins us as our CRM Architect, and Wilbert Kraan, our new Data Architect.  Both Jason and Wilbert have worked as consultants for several years and bring new skills and considerable experience to IS.  They both know more than I do about their respective fields, which is how I like to hire people.

So the Enterprise Architecture practice now comprises the three of us, instead of me working on my won, which means we have more capacty to guide the University's IT architecture.  We can offer a greater range of skills and can bring a wider range of experience to bear.  I'm really excited about the opportunities this presents.

As his job title implies, Jason will focus on contact relationship management, working to build a user community and to create a strategy for managing and improving the University's relationships with prospective students, research partners, community organisations, and other parties - to give them all a better …