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

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…