ShuttleCloud

Blog

The Cloud Ecosystem for Dummies

I’m not an engineer; I’m not even technical. But I work in the cloud space, and am therefore compelled to have a basic understanding of the industry in order to affect positive change.

By nature, “the cloud” is an intangible, inanimate array of products and services. With the industry experiencing a boom in growth from $60 billion to $241 billion in 2020 (Forrester), it is pertinent for consumers on every part of the ladder to acknowledge and familiarize themselves with the different elements of the cloud ecosystem.

Here’s a breakdown of the cloud marketplace:
cloud ecosystem
(image credit: techygeeks.org) 

As you can see, there are 3 major types of cloud services. Each have their own intended customer types, from end-user to developers and system admins. But it’s important to note that while customers may overlap between services, the service types don’t really overlap between customers.

See, pending the role of a service in an organization, the end customer has a specific function in their use of that service. For example, a software developer may use a PaaS such as Google App Engine to build a product, and then SaaS like Dropbox or even IaaS (Amazon Web Services) to store those project files.

But while service use cases are specific, they are rarely exclusive. The very notion of “ecosystem” has a connotation that brings all these components – SaaS, PaaS, and IaaS – together into a single cohesive unit of tools for cloud computing.

While you may only pay for or subscribe to one cloud component, the company behind that piece is likely utilizing the firepower of several other services to deliver your product. For example, Netflix customers (SaaS) are actually having their content delivered by Amazon Web Services, which is the massive data storage facility run by Amazon. Kind of fun to put into perspective that Amazon has their own cloud video streaming service, right?

You can see by the visualization above that each component builds on the one beneath it. Perhaps a better way to illustrate this is with the depiction below, which shows the measure of value visibility by end-users.

cloud computing value visibility(image credit: saasblogs.com)

Consider this vertical:

If Netflix is the SaaS, then Microsoft Silverlight (plugin required to stream video) is the PaaS, and AWS (for hosting the files) is the IaaS. The cloud ecosystem has been fully engaged, while the end-user is simply delivered content.

That’s all for now, but check back monthly for more posts on the debunking of cloud mystique.

Leave a comment

Your email address will not be published. Required fields are marked *

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>

  1. Two points of clarification might help this article better address its intended audience.

    1. The acronyms for Software as a Service (SaaS), Platform as a Service (PaaS) and Infrastructure as a Service (IaaS) should be defined up front.

    2. The statement, “By nature, ‘the cloud’ is an intangible, inanimate array of products and services” is vague and problematic. How will this definition possibly help the target audience to understand what the cloud actually is? The cloud may be “transparent” or possibly “obscure,” but is certainly not “intangible.”

    According to NIST (http://csrc.nist.gov/publications/nistpubs/800-145/SP800-145.pdf): “A cloud infrastructure is the collection of hardware and software that enables the five essential characteristics of cloud computing. The cloud infrastructure can be viewed as containing both a physical layer and an abstraction layer. The physical layer consists of the hardware resources that are necessary to support the cloud services being provided, and typically includes server, storage and network components. The abstraction layer consists of the software deployed across the physical layer, which manifests the essential cloud characteristics. Conceptually the abstraction layer sits above the physical layer.”

    a. Software as a Service. According to NIST: “The capability provided to the consumer is to use the provider’s applications running on a cloud infrastructure. The applications are accessible from various client devices through either a thin client interface, such as a web browser (e.g., web-based email), or a program interface. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings.”

    The SaaS is the most likely layer an end user or consumer will access. This is the actual application, such as a web-based word processor, e-mail, planner, bulletin board, etc. Examples: YouTube, Basecamp, Twitter.

    b. Platform as a Service. According to NIST: “The capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages, libraries, services, and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, or storage, but has control over the deployed applications and possibly configuration settings for the application-hosting environment.”

    Application developers will most likely use a PaaS to develop and host their SaaS. For instance, Heroku provides an entire application environment for developers and runs thousands of SaaS. The PaaS bridges the gap between the IaaS and the application developer so that the developer can focus on their application and need not worry about the configuration of that application environment (other than the configuration of their own application itself), as the PaaS takes care of it for them.

    I disagree that the Silverlight plugin is a PaaS, as it does not actually provide “the capability … to deploy onto the cloud infrastructure consumer-created or acquired applications …” If anything, it’s a plugin that extends the functionality of the Netflix SaaS, as it provides functionality on the consumer’s computer (the client) but does not provide any services in the cloud in and of itself, as it does not require its own server separate from a web server.

    Rather, the PaaS of Netflix is based on Hadoop, a “distributed file system” and “framework that allows for the distributed processing of large data sets across clusters of computers using simple programming models.”
    And the IaaS of Netflix appears to be Amazon S3.
    http://techblog.netflix.com/2013/01/hadoop-platform-as-service-in-cloud.html
    http://hadoop.apache.org

    c. Infrastructure as a Service. According to NIST: “The capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, and deployed applications; and possibly limited control of select networking components (e.g., host firewalls).”

    For example, Heroku runs on top of Amazon Web Services. Advanced developers who want to create their own PaaS or advanced applications that would be best served by the ability to customize the entire environment would be good candidates for using the IaaS directly, as opposed to a PaaS such as Heroku.

    In conclusion, acronyms should always be defined in articles intended for non-technical audiences, and the separations and relationships of the three layers, and the intended users of each, should be made clear.

    • Thanks Tom! Will be making changes to the article soon to reflect some of your great points.


Follow Us