Skip to main content

Cloud Computing Panel

I’ve just attended a panel session on Cloud Computing in Newcastle, which gave several points of view on the uptake and applicability of Cloud. The discussion covered Sofware as a Service (e.g; SalesForce, EMailCloud), Platform as a Service (e.g. Google App Engine, Arjuna) and Infrastructure as a Service (e.g. Flexiscale, Amazon EC2).

The optimistic view, taken by the majority of the panel, was that we are on a journey towards cloud computing becoming the norm for business computing. Duncan Mactear of 4Projects sounded a more cautious note; his company provides SaaS for the construction industry but does not use cloud; instead their servers are hosted in a third-party data centre. To which Tony Lucas of Flexiscale pointed out that 10 years ago, similar companies weren’t even using hosting services.

Sarat Pedirela of Hedgehog Lab, an ISV, pointed out that the appropriate infrastructure will depend on the type of application. Currently, Hedgehog use cloud for non-critical applications where the load varies greatly, such as downloading media files or running software configuration tests. Steve Caughey of Arjuna suggested that Cloud will be useful for any application where you can’t predict the demand. Ross Cooney of Rozmic agreed and added another example, of intense computations that can be sped up by running them in parallel.

All the panellists agreed that startup companies can particularly benefit, because they don’t need to install and run their own IT infrastructure. By way of contrast, Tony explained that some large companies have financial systems that can’t cope with variable IT costs; they want a fixed bill known in advance.

Trust was raised as a key issue. Several panellists opined that interoperability was the best answer to this; then if your provider has problems, you can switch your application to another. Rozmic run their EmailCloud application on both Amazon and Flexiscale, switching between them when one has problems. The downside of this is that it is currently expensive to implement applications for multiple providers, although some companies (such as CohesiveFT and Rightscale) are providing systems to aid this process.

All in all, it was an interesting and useful discussion. The session was arranged by Codeworks, with sponsorship from Flexiscale and Amazon.

Comments

Popular posts from this blog

Changing Principles

In EA, architecture principles set a framework for making architectural decisions.  They help to establish a common understanding across different groups of stakeholders, and provide guidance for portfolios and projects.  Michael Durso of the LSE gave a good introduction to the idea in a webinar last week for the UCISA EA community.

Many organisations take the TOGAF architecture principles as a starting point.  These are based on the four architectural domains of TOGAF: business, information/data, applications, technology/infrastructure.  These principles tend to describe what should be done, e.g. re-use applications, buy in software rather than build it, keep data secure.  See for example the principles adopted at Plymouth University and the University of Birmingham.

Recently though, I encountered a different way of looking at principles.  The user experience design community tend to focus more on how we should do things.  E.g. we should start with user needs, use iterative developm…

Why the UCISA Capability Model is useful

What do Universities do?

This may seem a strange question to ask and the answer may seem obvious.  Universities educate students and undertake research.  And perhaps they work with industrial partners and create spin-off companies of their worn.  And they may work with local communities, and affiliation bodies for certain degress, and they definitely report on their activities to government bodies such as HEFCE.  They provide student services and support.  The longeryou think about it, the more things you can think of that a University does.

In business, the things that an organisation does are called "capabilities", which is a slightly strange term.  I think it is linked to the HR idea of a combination of the CAPacity and ABILITY to do a task.  Whatever the name, it is a useful concept.  A capability is more basic than a process: a University may change the way it educates students but as long as it remains a University it will educate them one way or another.

A capability …

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…