Our DigitalScot.cloud guide provides a comprehensive overview for understanding Cloud computing and how best to apply it to improve your business.
This introduction explains the different types of Cloud service options, and how to select the right one for your particular requirements.
Cloud service layers
While this is initially quite confusing jargon, it’s actually a helpful guide to understanding what type of service is right for your business needs, especially so when combined with a simple mapping to who would use each one.
Plesk provides such a guide:
This highlights the Cloud ‘stack’, how one layer builds upon the lower service and in total makes up Cloud computing, with each layer being intended for different, increasingly less technical types of users:
IaaS – For system administrators who previously would have installed and built servers in their own local data centres. Now instead they can provision virtual servers in the global data centres of AWS or Microsoft.
PaaS – For the software developers who would then use those servers, to write business applications. PaaS provides them automation tools and services to streamline and speed their development workflows.
SaaS – Those business applications, provided online via a utility model (eg. priced per user). Previously they would have had to wait for the servers and applications to be installed and configured by technical staff, now they can set up them instantly themselves.
Another consideration is the “Pizza as a Service” analogy.
This compares the increasing scope of outsourced supplier services, how much management responsibility the provider owns versus what the customer manages, to how much work you do in the preparation of the pizza dinner.
This explains the scope of roles and responsibilities through an analogy ranging from ‘made at home’ right through full ‘dining out’.
So in the simplest of scenario exploration, small businesses are unlikely to be users of IaaS or PaaS, these are for larger organizations who have in-house teams of Sysadmins and Developers. AWS and Azure offer them powerful services at those layers that can greatly improve how they write and deliver software, and they want more control over this underlying technology.
In contrast small businesses typically don’t have those resources, so SaaS applications are ideal, as they require zero technical expertise to set up and use, and critically offer per user per monthly pricing options – They also don’t care how it is managed under the hood.
However for these same reasons SaaS is also equally useful to large enterprises. For example a marketing department who quickly needs a particular digital campaigning tool may not have the time to go through their internal processes and definitely not the months it would take to have developers create it from scratch. Again the primary value of SaaS is the quick, frictionless set up.
Cloud Service Selection
So fundamentally the decision of selecting the right Cloud service for your organization is a process of these different levels of user comparing the available options to their preferences and needs. AWS and Azure have varying IaaS features that will matter to Sysadmins, Developers have particular tools and ways of working that PaaS caters for in different ways, and business end users will have certain functionality they are seeking that can be compared to possible SaaS options.
As we reach the SaaS layer we find there are hundreds if not thousands of possible SaaS solutions available today, for any and all desired use case scenarios. FinancesOnline provides this very helpful list of just some of these, highlighting how these can be categorized by industry and functional features, from Accounting through HR, e-commerce and restaurant management among many others.
For a structured process of Cloud service selection, when the requirements are complex such as an enterprise organization, this presentation offers a framework for doing so within a context of business transformation.
Most notably they approach this from an Enterprise Architecture-led point of view, including encapsulating Business Architecture best practices too.
- How EA/BA provides the connecting logic between Strategy and Execution
- Mapping Strategic Goals on to relevant XaaS Cloud Services, through ‘Cloud Pattern Matching‘ (slide 50)
- Enterprise Architecture to Drive Cloud Strategy and Planning
- Business Value Driven Methodology
- slide 20 – connecting business strategy to technology investments
- Embraces and extends proven Cloud best practices, from NIST, Cloud Security Alliance, et al.
Cloud Pattern Matching: ‘XaaS Mapping’
Cloud Solution Design can fundamentally be thought of as a process of “XaaS Mapping”, refering to identifying which particular type of Cloud service might be the best fit for your particular business requirement(s).
In the Microsoft presentation on slide 50 they show this XaaS Mapping, which they describe as ‘Cloud Pattern Matching’.
The customer requirement, eg ‘A1: Customer Portal‘, is matched to a Public SaaS option. Other elements may then be mapped to on premise functionality, and the capability needed to integrate them also defined as a canvas requirement and also mapped to a Cloud service.
This can be applied right through to scenarios including private, in-house deployments, with a common function of each mapping being the exposure and linkage to the underlying enabling technologies in a uniform fashion, across Cloud, SaaS and internal apps.