You may already know the cloud as a service model, but to make full sense of the buzzwords and concepts circulating in today's industry, it's essential to view the subject from multiple angles. Let's guide you through these different perspectives, clarifying what terms like 'cloud-native,' 'hybrid cloud,' and 'multi-cloud' actually mean, and how their meanings can shift based on context and viewpoint.
THIS IS AN INTERACTIVE PAPER, SO PLEASE LOOK OUT FOR HINTS ON HOW TO DRILL DOWN AS YOU EXPLORE
CLOUD
CONFLATION AND
CONFUSION
Cloud Native
Cloud First
Multi-Cloud
Hybrid-Cloud
Public Cloud
So how did these various interpretations stack up with your own view? The chances are that you agreed with some, were surprised by others, and considered some of the takes nonsensical or flat out wrong. And that sums up the problem.
Navigating the Jargon Maze
The first key to navigating cloud terminology maze is to shift your perspective from systems to services. This change in mindset is central to understanding the essence of 'cloud'. Also recognising that services can be delivered through both your data centre and external providers allows you to focus on the nature and quality of the services themselves, separately from their location or source.
If we then add architecture into this mix, it becomes much easier to understand and compare different forms of cloud computing.
While there are many ways to dissect a cloud solution or service to understand its characteristics, the schematic below captures some of the main dimensions to consider. Tap on any of them see the kind of questions to ask in each area when evaluating or comparing different options
Type of Service
Hosting Location
Source & Delivery
Service Architecture
Contract & Commercial
The dimensions we’ve outlined are mostly independent of each other and the options within each can be combined in many different ways - and in practice they are IT vendors and service providers innovate to deal with different requirements and use cases.
This is why a lot of labels and categories we discussed at the outset aren’t that useful in practical terms. To understand and compare different supplier propositions, you have to consider each of the dimensions we’ve outlined. Make assumptions, and there’s high risk of being caught out.
To finish on a positive a note, however, it’s nowadays possible to define a ‘cloud’ solution to meet pretty any set of requirements. So don’t start by asking whether public, private, hybrid or any other form of cloud is right in a given context; define what’s important in terms of functionality, performance, cost, control, security, compliance and so on, then talk to suppliers about meeting your specific needs.