Journal The Cost of Cloud

A very sensible - and refreshing - article weighing the trade-offs of moving infrastructure1 into “the cloud”.

It doesn’t get into the detail of capital vs. operational budgets but highlights that weighing the above many organisations still save due to inefficient and overpriced traditional legacy infrastructure (making the argument for in-house infrastructure reform).

If you’re using commercial virtualization platforms and/or SAN storage, then you’re overpaying by as much as a factor of 10, and getting an inferior product into the bargain - so that while many organizations could save a huge amount of money by moving to the cloud, they could save even more by running their internal operations better.

Relevance to health and care

However the real take home message from the article is trade-offs aside using “the cloud” enables organisations to reduce the time spent outside their core competencies. This is where the fundamental ideological augment needs to be made in health and care - technology is a core competency.

This can be hard to understand surely the core competency is providing health and care? Supermarkets are a good example of a similar perception problem - their core competency is selling food surely? Wrong - they are specialised logistics companies (and like logistics companies entirely dependent on in-house technology to run their operations).

In-house capacity to build and maintain the digital tools needed to run a modern health and care organisation are essential for both the cost and agility benefits that are simply not possible within the current entrenched market. We must fund teams not projects to maintain and grow this capacity.

  1. A distinction needs to be made here between “moving infrastructure to the cloud” and buying so-called “cloud hosted” software-as-a-service and calling this “moving to the cloud”. This article discusses the former not the later. 

Last Update
Update History 381
  • Publish Journal posts