Skip to main content

Webinar: Virtualisation and Service-Oriented Architecture - Building a cutting edge IT Infrastructure

On Thursday (April 19th) I will be hosting another in our series of webinars. This week's seminar will feature case studies of two core technologies for building a cutting-edge infrastructure. Zafar Chaudry will describe how he used virtualisation to consolidate his disparate servers and storage provision into a manageable and scalable infrastructure. Then Mark Simpson will show how he deployed a service-oriented architecture to give a major financial institution far more control and scalability over its business processes.

Zafar and Mark come from very different sectors. Zafar is at the Liverpool Women's Hospital while Mark works for the business IT consultants Griffiths-Waite. I find it fascinating to see just how broad is the uptake of these new techniques - they really seem to be applicable across most sectors. This will be one issue that I'll explore in the discussion on Thursday. I'll also ask Mark and Zafar to comment on how virtualisation and SOA interact in more complex infrastructures - my belief is that complement each other well.

I'll be taking questions during the broadcast but you're also welcome to send me any in advance as well. The broadcast will be at 2:30 on Thursday and you can register to attend at http://mediazone.brighttalk.com/event/gridcomputingnow/7eacb53257-419-intro .

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 …

Service Excellence, Digital Transformation and Enterprise Architecture

Our University Secretary has sponsored a major review of the University’s administrative processes, coining the banner “Service Excellence”.  The aim is to look at the services we provide to staff and students with a fresh eye, making them more effective, more efficient, and focussed on the user rather than administrative convenience.

Our CIO is sponsoring a similar programme called “Digital Transformation”. This will replace old paper-based processes, starting with the question of what would processes look like if we designed them afresh for the modern connected world.  The aim is to make processes that are more focussed on the user and hence more effective and efficient.

Both of these ambitious programmes will need an effective enterprise architecture, if they are to succeed.  Digital Transformation is intrinsically about using opportunities provided by new technology to improve services and, as such, it requires effective technology services to make data available when needed, to pro…

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…