This is the second and final installment of our series Breaking down the Cloud. Today we explore different Cloud Service Models. See Part I by clicking here.
Cloud Infrastructure Components
Now that you know what the Cloud is, let’s dive into the nitty-gritty details of cloud software and application infrastructure.
- Datacenter – The site where the Cloud solution is physically located.
- Network – A group of two or more computers linked together that carry communications between systems and (usually) the Internet.
![cloud computing image]()
- Hardware – The physical, tangible unit that provides the storage and central processing unit (CPU).
- Virtual Machine (VM) – Emulating multiple physical machines, the VM runs the Operating System (OS).
- Hypervisor – Also known as the Virtual Machine Monitor, this optional element creates and runs VMs. If this component is not employed, the OS processes from the hardware component.
- Solution Stack – Many programs bundled together to complete a task.
- Application – The actual application being used by those who run the Cloud or their customers.
- GUI or API – The interface with which the end-user interacts.
With the power of these components combined, your basic cloud is formed.
Dispersing the Responsibility: Cloud Service Models
Managing all of these components is a big responsibility. That’s why there are different types of Cloud Service Models.
There are three major Cloud Service Models: Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (Paas) and Software-as-a-Service (Saas). Organizations and individuals select a Cloud Service Model based on their needs and resources. With some, the organization or end-user manages components and so does the service provider. In others, the organization or end-user manages little to nothing while the service provider manages almost everything.
Infrastructure-as-a-Service (Iaas)
In an IaaS deployment, the customer is responsible for the VM, Solution Stack, Application and API/GUI. The provider supplies the storage, networking and other information technology (IT) infrastructure. This option is optimal if a company wants more control over their software and has the resources and people to manage these components.
This diagram shows how the responsibility of managing individual cloud components is dispersed between the provider and the consumer in an IaaS:
A popular IaaS pr
ovider is GoDaddy, which offers basic domain and website services in addition to hosting and server management. People who decide to open a new website or domain with GoDaddy rely on GoDaddy’s hosting and server management.
Platform-as-a-Service (Paas)
In a PaaS deployment, sometimes called Middleware, the providers supply the infrastructure components plus the Platform and Solution Stack to customers. Many software companies deploy their solution this way because developers have the flexibility to build and operate their applications without breaking the bank due to high IT costs.
This diagram shows how the responsibility of managing individual cloud components is dispersed between the provider and the consumer in a PaaS:
Gizmox‘s
Visual WebGui is one of the most popular PaaS suppliers, providing an enterprise HTML5 platform for developers to construct, transfer, run and manage applications for the cloud and/or mobile devices.
Software-as-a-Service (Saas)
This is the model you are likely to use most often. Usually accessible via the Internet, applications are distributed as a service rather than on-site; they are hosted remotely and you as the consumer access it through the web. In this model, the end-user only interacts with the GUI/API (through a browser) to access the web-based application, and doesn’t have to worry one iota about the rest of the components.
This diagram shows how the responsibility of managing individual cloud components is dispersed between the provider and the consumer in an SaaS:
In a vast sea of web-based SaaS providers, Salesforce.com is one of the largest and well-known. This popular Customer Relationship Management (CRM) system enables their customers to manage their accounts, sales prospects and interactions through their application on the Cloud.
The beauty of the Cloud is that at the end of the day, there is a lot of flexibility in choosing the amount of control you want over back-end processes AND you save resources.
Similar but Different
Here’s a look at all three of the Cloud Service Models next to each other; notice the different balances of responsibility and control between the user(s) and the provider.
RJS Cloud Solutions
Here at RJS we offer an SaaS model for several products that can help your company eliminate hiccups, headaches and hardware costs by managing your business’ documents and data in the Cloud. Our secure, cloud software solutions fully integrate with ERPs and custom business applications to make sure your current business processes run smoothly. Learn More>>
Lessons Learned
Now you know what the Cloud is and how it differs from traditional on-premises software. You can also differentiate between the major Cloud Service Models. Hopefully, this newly acquired knowledge will help you navigate through the horde of providers and their services to reach the solutions that are right for you.
If you have questions on the Cloud, or are interested in our Cloud Services, please contact us at sales@rjssoftware.com or (888) 757-7638.
This is the second and final installment of our series Breaking down the Cloud. If you missed Part I, divulging the differences between the Cloud and On-premises Software, read it.
