Cloud Service Models With Examples – Guess what, sometime in recent years, most of us have seen versions of graphs comparing cloud computing service models (IaaS, PaaS, SaaS) and on-premise environments? Did you know that we use the visualization of four software layers (layer cakes) to describe the differences between infrastructure, platforms, and the software “-as-a-service” model, as described in the NIST definition of cloud computing?
At the time of this writing, it has been nearly 10 years since the initial announcement of Microsoft Azure (later called “Windows Azure”) by Ray Ozzie at the Microsoft Professional Developers Conference 2008 (PDC08) on October 27, 2008. If you remember, this was something Microsoft couldn’t imagine at the time. After all, only the cool kids on the Amazon and Google blocks are interested in cloud computing. Additionally, consider that the subscription-based revenue model has the potential to cannibalize many of Microsoft’s existing license-based products.
Cloud Service Models With Examples
After the announcement, public interest in learning about Azure has been immense. According to my records, I personally held 300 meetings with companies of all sizes in the 6 months following the announcement.
Services Provided By Saas Providers Cloud Service Models It
Presentation slides were a big part of my work at that time, as visual aids helped explain many concepts and details and facilitated conversation. In one of the slide decks I used, there is this diagram (found on Slideshare dated November 19, 2008):
It is used to describe the platform-as-a-service (PaaS) approach that Azure implements. If you recall, at the time Azure only had web roles and worker roles (as classic cloud services are categorized today) as the primary compute options. It is a service running on the PaaS model, at which point we need to rationalize/justify the fundamental differences in the PaaS model regarding the way people perceive local IT. This diagram helps to reveal the main trade-offs between the popular models at the time: on-premise, outsourced hosting and (new) public cloud environments.
The first diagram briefly highlights the key differences and helps people recognize that PaaS is different from outsourced hosting and on-premise IT. But that only refers to the topic at the surface layer; We often spend a lot of time discussing how and why PaaS is different – not just by language, but by IaaS. So we needed a different visualization to support that part of the conversation.
Our approach is based on a visual representation of the existing local IT environment and a cloud service model mapped to the same environment so that differences can be highlighted in the context of similarities (map as opposed to stating them explicitly in the preceding words). Therefore, using a high-level common IT infrastructure domain that is consistent across all models, a 9-layer hierarchical view is developed. Specific layers were chosen because they abstract some level of concern, and represent a traditional IT stovepipe layer representation, with few direct dependencies or design/functional abstraction between layer layers.
The Shared Responsibility Model For Cloud Security
After several iterations, this view was created, originally published on my MSDN blog (dated January 13, 2009):
(A side note) The dependencies and separation aspects of concern between layers are often lost when trying to use other models to visualize these layer relationships, such as pizza-as-a-service and car-as-a-service. To me, these analogies make the map more interesting, but ultimately miss an important part of the context.
And the use of warm color (red pieces) vs. The cool color, and the number of layers raised per model, all visually invite and explain the level of differences (eg, Locale has 9 red layers, IaaS only 4 and PaaS 1 – indicating that they are more different than similar; oh, and PaaS’ cool’).
As this view gained traction, a version of it was published on SlideShare (dated June 9, 2009). To help people understand the impact of these model differences, here’s a car analogy mapped to the same 3-column structure.
Intellectual Property In The Cloud
Essentially, it still maps the initial high-level exchange messaging between ‘control’ and ‘economy of scale’, but is now visually easier to understand and helps facilitate more engaging discussions during presentations.
In the following months, from a visual design perspective, rich, 3D-looking graphics (eg gradient boxes, lighting, bevels, borders, corners, shadows, effects, etc.) will move towards flatter. , simple design. This chart has also been updated to reflect these trends (Slideshare (17 October 2009)); Now less complex objects (less visual noise), and fewer colors (simpler palette).
By this time, a lot of people had seen these graphs, as their use was proliferating in public, and as, within Microsoft, we fully embraced the cloud, legions of Microsoft employees and partners began blogging and pitching about Azure. Among the many comments received, one came from Scott Kerfoot, who suggested adding a fourth column to represent software-as-a-service (SaaS).
Adding SaaS meant we had to modify the model a bit, mainly because we needed to distinguish between PaaS and SaaS, because it didn’t work to have only one layer of difference between the two, and we still needed to maintain that level of differentiation. Two. Relatively stable models. Removed “Security & Integration” and added “Data” under “Applications” due to security concerns across all layers. Later “database”, “server” and “HW server” were replaced by “middleware”, “O/S” and “server”; each one.
Saas Vs Paas Vs Iaas: What’s The Difference & How To Choose
Later this view was created (January 15, 2010), with a standard 2-tier distinction between SaaS, PaaS and IaaS; And the 5-layer distinction between IaaS and on-premises suggests that cloud environments are different than on-premise environments.
Further flattening and simplifying the graphic design of the diagram, and some minor corrections, such as changing “O/S” to “Operating System” and “On-Premises” to “Traditional IT” (we need to distinguish from context), and O/ in IaaS. Adjusting the ‘managed’ line a bit to express a view of shared responsibility for S (the cloud vendor provides the base VM image, but the customer still needs to maintain it, patching and updating etc.), we arrive at the final version file shown below (similar to the one at the top of this post).
This version is published and distributed through multiple sources, and my presentation suite is mostly updated in technical details, so it’s not published to avoid too many duplicates (since I already have more Azure overview suites on SlideShare). Later in 2011 when I wrote about the cloud ecosystem, this last version was mentioned.
Progress in this field is moving fast. The conversation quickly shifted from explaining and justifying PaaS to deeper discussion and engagement about actual development plans. The lines between IaaS and PaaS started to blur even before Azure created Virtual Machines in 2012 (Azure has had VM roles since 2010, but it’s not really IaaS). It is increasingly about building capabilities in cloud projects regardless of which ‘cloud model’ a particular implementation uses (eg APIs, components, features, services, etc.). Application plans create services and features built on top of IaaS and PaaS options. It is no longer IaaS or PaaS; That’s IaaS and PaaS and SaaS. Additionally, as maturity around hybrid cloud approaches increases, the lines between on-premise environments are also blurring.
What Is Paas (platform As A Service)?
So this diagram will not be part of my standard cloud computing presentation. However, it continues to be referenced and widely used in the cloud computing literature in various forms. Some of the core content has been updated frequently over the years, but it’s interesting to see how these charts are still used by people today.
A simple image search on “iaas paas” will turn up hundreds of clicks from all kinds of sources around the world and in many variations and flavors and in many languages. Some claim to have created this view, some credit the “Internet”; Most of the time it is merely visual without citing any evidence. It is interesting to see how this unit of work takes on a life of its own. Cloud computing is taking the world by storm. In fact, according to Cisco Research, 94% of workloads and compute instances will be processed by cloud data centers by 2021, compared to only 6% by traditional data centers.
The concept of cloud is not new, but as more companies and businesses turn to cloud-based services, it is important to understand the nuances of cloud computing terms and concepts.
For non-techies, the cloud can be an intimidating and awkward concept. We always hear about cloud computing, but what does it really mean?
Cloud Security Functions
Cloud computing is a model of service provider communication that enables convenient, on-demand network access everywhere.
In short, the cloud is the Internet and cloud computing is a texspeak to describe the software and services that run on it.