The recent Cloud World Forum in London provided plenty of food for thought. I have already talked about some of the challenges for customer and organisations. The industry transformation being wrought by cloud computing also creates some interesting career choices for programers and other IT specialists.
This is the second post about some insights I gathered from attending the Cloud World Forum in London in June. The first post covered some uncomfortable choices for cloud customers. This post explores the equally unpleasant choices for suppliers.
I managed to get along to the Cloud World Forum in London this week. It was a busy, fast and noisy event (sometimes very noisy) which provided a way to sample a lot of views in a short space of time. The fundamentals of cloud computing are well established so there were no paradigm shaking revelations (and this wasn’t the kind of premier global event where such things might get announced anyway). I did pick up some subtle signals which might be of interest to organisations wanting to move to the cloud, suppliers competing for cloud business and engineers working with cloud technologies. This first post focuses on the customer perspective.
Despite what you might have heard, managing finances for IT is really very simple. Forget the nonsense you may read about “value centres” and “capex vs opex”. Instead, here is a simple story which will illustrate all you need to know.
Guest post by Daniel Smithson Don’t incur technical debt with the cloud – employ a cloud abstraction product The arrival of cloud technologies has led to a gold rush of adoption. Cloud technologies appear to offer organisations the nirvana of rapid, on-demand elastic compute provision, be that through public, private or hybrid deployments. Having embraced the benefits of self-service infrastructure, organisations are now embarking on developing cloud-centric applications that harness the ability of the cloud to expand and contract infrastructure capacity based on application demand. However, to do so applications need to be coded to exploit the API of the chosen cloud platform. And this may have a sting in the tail - technical debt.