Any views expressed within media held on this service are those of the contributors, should not be taken as approved or endorsed by the University, and do not necessarily reflect the views of the University in respect of any particular issue.

Enterprise Architecture

Enterprise Architecture

Discussion and news from the Enterprise Architecture (EA) service

The cloud is not a place

At a local meetup last week, Steven Bryen of Amazon gave a summary of the recent changes to the AWS cloud platform. This was a very useful reminder of what public cloud platforms offer us.

Five or ten years ago, discussion about whether to move IT to the cloud was primarily about location – whether it is worth running your own data centres when commercial companies can run them more efficiently. These days, “the cloud” is an operating model, not a place.  Cloud is a way of writing and deploying applications so that they can be dynamically deployed to meet changing demand, can access a range of libraries such as image or text recognition (sometimes using specialised hardware), can be upgraded without downtime, and similar beneficial characteristics.

I’m reminded of when I worked on grid computing, back in the 2000’s. Back then, some people talked about the idea of utility computing, presenting a future in which you could  plug a local PC into computing capacity provided as a utility, in much the same way you can plug a device into the power grid without needing your own generator. With public cloud computing, that future arrived a few years ago.

What doesn’t work is to simply move your existing applications onto a public cloud platform without modifying them. (This is a process sometimes called “lift and shift”). Industry experts advise us that companies who have done this have experienced several problems, which can include increased costs and reduced performance from the network, or reduced resilience because cloud platforms implement resilience in a new way. Sometimes, users have had to pay substantial amounts to retrieve their own data.

The challenge for us is two-fold. On the infrastructure level, we will most likely follow a hybrid approach, providing a cloud platform that can use both in-house and public cloud infrastructure. As a research university, we have an ongoing need for on-site infrastructure, and with the data centres already in place, we can run a cloud platform on-site at reasonable cost, while using public cloud provision to scale up and to provide resilience.

Diagram showing applications moving between an on-site cloud and a public cloud

On the applications level, we need to write (or re-write) our applications to take advantage of cloud computing platforms, wherever they may be, and to support our staff development where necessary so that we have the knowledge and skills to develop and manage applications in the new world.

We are a little behind the curve and we need to catch up.  On the positive side, we can learn from other people’s experiences and avoid making the same mistakes.

Leave a reply


Report this page

To report inappropriate content on this page, please use the form below. Upon receiving your report, we will be in touch as per the Take Down Policy of the service.

Please note that personal data collected through this form is used and stored for the purposes of processing this report and communication with you.

If you are unable to report a concern about content via this form please contact the Service Owner.

Please enter an email address you wish to be contacted on. Please describe the unacceptable content in sufficient detail to allow us to locate it, and why you consider it to be unacceptable.
By submitting this report, you accept that it is accurate and that fraudulent or nuisance complaints may result in action by the University.