Cloud Models - CompTIA A+ 220-1001 - 4.1

Summary

This video script explores various cloud computing models, including Infrastructure as a Service (IaaS), Software as a Service (SaaS), and Platform as a Service (PaaS). It explains how IaaS offers hardware while leaving software management to the user, SaaS provides ready-to-use applications managed by a third party, and PaaS offers a platform to build applications without worrying about infrastructure. The script also covers deployment models like private, public, hybrid, and community clouds, and discusses the cost structures of internal vs. external clouds. It highlights cloud benefits such as rapid elasticity, on-demand self-service, resource pooling, and the ability to measure application performance.

Takeaways

• 🌟 Cloud computing offers various models to configure applications, each with distinct responsibilities and services.
• 🛠️ Infrastructure as a Service (IaaS) provides hardware resources, but users are responsible for software installation and management.
• 🌐 Software as a Service (SaaS) allows immediate access to applications through a third-party provider, who handles maintenance and data security.
• 🏭 Platform as a Service (PaaS) is a middle ground, offering a platform to build applications without worrying about underlying infrastructure.
• 🏢 Private cloud deployment involves owning all components and building your own cloud environment, with no resource sharing.
• 🌍 Public cloud deployment is accessible to anyone on the Internet, like Amazon Web Services or Microsoft Azure, with shared resources.
• 🔄 Hybrid cloud combines private and public cloud services, allowing for flexibility in resource allocation and data management.
• 👥 Community cloud deployment involves multiple organizations sharing resources to create a larger cloud, reducing individual costs.
• 💰 The cost of cloud services can vary from flat fees for non-metered services to hourly rates for metered services, affecting budget planning.
• 📈 Cloud applications can exhibit rapid elasticity, scaling resources up or down based on demand fluctuations, without user intervention.
• 🚀 On-demand self-service is a key feature of cloud services, enabling the quick provisioning of new servers or applications with minimal setup.
• 📊 Resource pooling and measurement are facilitated by cloud services, allowing for efficient use of hardware and detailed monitoring of application performance and costs.

Q & A

What are the different cloud models mentioned in the script?

The script mentions three main cloud models: Infrastructure as a Service (IaaS), Software as a Service (SaaS), and Platform as a Service (PaaS).

What does IaaS provide and what are the responsibilities of the user?

IaaS provides all the hardware needed to run applications, but the user is responsible for installing applications, operating systems, managing software, data, security, and maintenance.

Can you give an example of a common implementation of IaaS?

A common implementation of IaaS is a web hosting provider, where the user purchases hardware and is responsible for installing and maintaining web hosting software and websites.

How is SaaS different from IaaS?

SaaS is a model where the user logs into a website to access the software immediately, without the need to install or maintain it. The third-party provider handles application maintenance, data safety, and other associated tasks.

What is an example of a SaaS application mentioned in the script?

Google Mail is given as an example of a SaaS application, where users can log in to access mail services without any programming or maintenance responsibilities.

What is the role of the user in the PaaS model?

In the PaaS model, the user is in charge of building their own application but does not need to worry about other aspects of the infrastructure, such as servers, software, or data centers.

How does Salesforce.com utilize the PaaS model?

Salesforce.com offers a PaaS by breaking their SaaS offering into different modules, allowing users to customize their application by combining these modules in a way that suits their business needs.

What are the different deployment models for cloud-based services discussed in the script?

The deployment models discussed are private cloud, public cloud, hybrid cloud, and community cloud.

What is the difference between an internal and an external cloud in terms of cost and resource sharing?

An internal cloud involves owning all resources without sharing, with upfront costs for hardware and infrastructure. An external cloud involves sharing resources with others on a public cloud, with no large upfront cost but with variable usage-based costs.

What are the unique characteristics of cloud-based services mentioned in the script?

The unique characteristics include rapid elasticity, on-demand self-service, instant resource provisioning, and resource pooling, along with the ability to measure and monitor various aspects of the application.

How does rapid elasticity benefit cloud-based applications?

Rapid elasticity allows cloud-based applications to scale up or down based on demand, adjusting resources as needed without the end users being aware of the changes behind the scenes.

What is on-demand self-service and how does it benefit users?

On-demand self-service is the ability to quickly add new servers, networks, or applications by clicking a few buttons, without the need to purchase or install physical hardware, providing instant resource provisioning.

How does resource pooling in cloud-based services optimize resource utilization?

Resource pooling allows for the efficient use of a large piece of hardware by virtualizing multiple servers within it, enabling idle times of one server to be utilized by another, thus optimizing resource usage and reducing waste.

Outlines

00:00

🌟 Cloud Computing Models Overview

This paragraph introduces various cloud computing models, starting with Infrastructure as a Service (IaaS), where users are provided with hardware but are responsible for the software and data security. It then contrasts this with Software as a Service (SaaS), where third-party providers manage applications and data, offering immediate access like with Google Mail. Platform as a Service (PaaS) is presented as a middle ground, allowing users to build applications without managing infrastructure, exemplified by Salesforce.com's customizable service modules. The paragraph also touches on different deployment models including private, public, hybrid, and community clouds, each with distinct ownership and cost structures.

05:02

💳 External Cloud Deployment and Cloud Service Characteristics

The second paragraph delves into the specifics of external cloud deployment, highlighting the absence of large upfront costs and the presence of metered or flat-rate costs for services. It discusses the flexibility of cloud services, such as rapid elasticity to scale resources based on demand, and on-demand self-service for instant resource provisioning. The paragraph also explains the concept of resource pooling to maximize hardware utilization and the ability to measure application usage for cost estimation. Additionally, it covers the challenges of traditional application deployment and how cloud services provide a near-instantaneous solution to these issues.

Keywords

💡Cloud-based applications

Cloud-based applications refer to software programs that are hosted on remote servers and accessed over the internet rather than being installed on local devices. In the video, it is the central theme, discussing various models for configuring these applications, such as IaaS, SaaS, and PaaS, which are essential for understanding the cloud computing landscape.

💡Infrastructure as a Service (IaaS)

Infrastructure as a Service, also known as Hardware as a Service (HaaS), is a cloud computing model where the provider offers virtualized computing resources over the internet. The video explains that with IaaS, users are responsible for installing and managing their applications and operating systems, while the provider supplies the necessary hardware infrastructure.

💡Software as a Service (SaaS)

Software as a Service is a cloud computing model where a provider hosts applications and makes them available to customers over the internet. The video mentions SaaS as an on-demand software model where users can log in to a website and immediately access the software, with the provider handling maintenance and data security, exemplified by Google Mail.

💡Platform as a Service (PaaS)

Platform as a Service is a cloud computing model that provides a platform allowing customers to develop, run, and manage applications without the complexity of building and maintaining the infrastructure typically associated with developing and launching an app. The video describes PaaS as a middle ground between IaaS and SaaS, where users focus on the application development while the provider manages the infrastructure.

💡Web hosting provider

A web hosting provider is a company that offers space on its servers for individuals and organizations to store their websites. In the context of the video, it is mentioned as a common implementation of IaaS, where the provider supplies the hardware, but the user is responsible for installing and maintaining the web hosting software.

💡Rapid elasticity

Rapid elasticity is the ability of a cloud-based service to scale up or down quickly in response to changing demand. The video explains that this feature allows applications to adjust resources as needed, such as allocating more resources at the end of the month when usage is higher, without the end users being aware of the changes behind the scenes.

💡On-demand self-service

On-demand self-service is a characteristic of cloud computing where users can provision computing resources without requiring human interaction with the service provider. The video illustrates this concept by describing the ability to spin up a new server or application instantly through a few clicks, without waiting for physical hardware or software to be available.

💡Resource pooling

Resource pooling is a cloud computing concept where multiple consumers share a common set of computing resources, which are dynamically assigned according to demand. The video discusses how cloud services allow for the efficient use of resources by pooling them together, enabling the use of idle times from one server to support another.

💡Metered services

Metered services in cloud computing refer to a pricing model where users pay for what they use, with costs being measured in units such as hours of computing time or data storage. The video explains that with metered cloud services, there can be costs associated with various actions like uploading, downloading, or storing files.

💡Flat cost

A flat cost is a fixed fee paid over a certain period for a service, regardless of usage. In the video, it is contrasted with metered services, where the script mentions that non-metered services might involve a flat fee for storing files in the cloud, allowing for unlimited uploads or downloads within that fee.

💡Hybrid cloud

A hybrid cloud is a deployment model that combines both private and public cloud services, allowing data and applications to be shared between them. The video describes a hybrid cloud as a combination of services running in a private data center and those running in a public provider's cloud, offering flexibility and the ability to leverage the strengths of both deployment models.

Highlights

Different ways to configure cloud-based applications.

Infrastructure as a Service (IaaS) provides hardware but requires user management of software and data.

Web hosting providers are a common example of IaaS.

Software as a Service (SaaS) allows access to software without development work from the user.

SaaS providers handle all maintenance and security, such as with Google Mail.

Platform as a Service (PaaS) allows users to build applications without managing the infrastructure.

PaaS provides building blocks for application development, exemplified by Salesforce.com.

Different cloud deployment models: private, public, hybrid, and community.

Private clouds involve owning and managing all hardware and software.

Public clouds are available to anyone on the Internet, like Amazon Web Services.

Hybrid clouds combine private and public cloud resources.

Community clouds share resources among multiple organizations.

Internal clouds require upfront costs for hardware, while external clouds have usage-based costs.

Rapid elasticity allows scaling resources based on demand.

On-demand self-service enables quick provisioning of new servers and applications.

Resource pooling maximizes hardware efficiency by virtualizing servers.

Cloud services provide detailed metrics for usage and cost measurement.

Metered cloud services charge based on usage, while non-metered services charge a flat fee.

Cloud-based services enable near-instantaneous deployment of applications.

Cloud services offer the flexibility to allocate resources dynamically based on usage patterns.

Transcripts

We often make generic references to the cloud.

But in reality, there are many different ways

to configure your cloud-based applications.

In this video, we'll look at some of these cloud models.

One type of cloud model is infrastructure

as a service or IaaS.

You may see this sometimes referred to as hardware

as a service or HaaS.

This is a cloud model that provides you

with all of the hardware that you might

need to run your applications.

But you're still responsible for installing those applications,

perhaps even installing the operating system that's going

to run on those computers.

And you also are in charge of managing all

of that software and the data.

Although the data is in the cloud,

you're the one who's responsible for the security

and the maintenance of all of that information.

One common implementation of infrastructure as a service

is a web hosting provider.

You purchase the hardware from that web hosting provider.

But you're responsible for installing

the web hosting software and maintaining

all of your websites.

Another popular cloud model is software as a service or SaaS.

Software as a service is sometimes

referred to as on-demand software.

You log into a website and you immediately

have access to the software.

For example, a third party SaaS provider

might provide you with email distribution

or maybe all of your payroll services

are done by logging into software as a service provided

by a third party.

And they handle all of the rest of the payroll process.

With software as a service, the application and the data

are all maintained by the third party provider.

This cloud-based provider is going to be responsible

for the maintenance of the application,

for keeping all of your data safe,

and everything else associated with that application.

This is usually a complete offering.

There's no development work that you would have to do.

You simply log into the service and it's available to you.

One common software as a service is Google Mail.

You log into the Google Mail front-end,

and all of the mail services are available to you.

You don't have to provide any programming or any maintenance

of that data.

Google handles everything from their end

with software as a service.

A good middle ground between infrastructure

as a service and software as a service

is platform as a service or a PaaS.

With platform as a service, you're

in charge of building your own application.

But you don't have to worry about any other aspect

of the infrastructure.

You don't worry about the servers or the software

or the data center.

You can concentrate on building the application

and have the platform as a service provider handle

every other part.

This means that all of your applications are in the cloud.

You don't control the people managing those applications.

You don't control the hardware.

You're only responsible for putting together

the development process for the application.

We often think of platform as a service

as a series of building blocks.

Instead of you building an entire application

from the ground up, platform as a service

gives you all of the modules that you need to put together

to build your own application.

A good example of this is the platform

as a service offerings available through Salesforce.com.

Salesforce.com is a very popular software as a service offering.

But they realized they could break

that software as a service offering into different modules

and allow you to put the modules together in a way that

makes sense for your business.

And so they not only provide their software

as a service offering, but they also provide a platform

as a service offering that gives you complete customization

of your application.

There are different deployment models

for cloud-based services.

One is that you have all of your own components

and you build your own private cloud.

You would own all of the hardware in your own data

center.

And all of your cloud-based services

would be virtualized in an environment that you control.

A public cloud deployment model is

one that's available to anybody on the Internet.

If you're using Amazon Web Services or Microsoft Azure,

then you're using a public cloud-based service.

If you're combining these models together,

you might have some part of your cloud-based services

running in a private data center and other aspects

of your cloud-based service running in a public provider's

cloud.

In those scenarios, you would have a hybrid cloud.

If you'd like to share the cost and resources associated

with the cloud, you may want to get a group of organizations

together to share that cost.

That model is a community deployment model

where many organizations can create a much larger cloud

and then share those resources between the members

of the community.

The cost of deployment of using an internal cloud

or an external cloud are quite different.

With an internal cloud, all of the resources that you're using

are yours and yours alone.

You're not sharing those resources with anyone else.

You also have to build your own cloud, which

means you have to pay for everything upfront.

You have to purchase all of the hardware and all

of the networking structure in order to build out that cloud.

Once you purchase the hardware, there's no ongoing costs

except for those associated with power

and maintaining cooling in the data center.

With an external cloud, you're sharing resources

with everyone else is on that public cloud.

But you don't have to purchase any of this hardware.

There's no large upfront cost required in order

to use the resources on an external cloud.

There is, of course, a cost to use the cloud.

And those costs may be metered where

you pay a certain amount per hour

or there may be a large upfront cost

that you use to be able to take advantage

of that external cloud.

With metered cloud services, there

can be a cost for almost anything

you would do on that service.

If you upload a file, there's a cost.

If you download a file, there's a cost associated with that.

If you store the file on that cloud service,

there's another cost associated with that.

So depending on how your application works,

you may want to look to see what type of metered costs

would be associated with using that application in the cloud.

With non-metered services, you're

generally paying a flat cost over a certain amount of time.

So you might have a flat cost to store files in the cloud.

And you can upload or download that file as many times

as you'd like.

And you pay a flat fee.

Once we have an application running in the cloud,

there are a number of unique characteristics

that we can then associate with that application.

For example, if we have an application that

has a lot more use at the end of the month than the beginning

of the month, we can change the number of resources

available for our users.

For example, we may have an application

that is very busy at the end of the month

but is not very busy at the beginning of the month.

So we might want to allocate more resources

available to that application as the end of the month

is approaching.

This is called rapid elasticity where

we can scale up or scale down the application resources as

needed.

This is all done behind the scenes.

And it's invisible to the end users.

All they know is the application works for them

whether it's the beginning of the month

or the end of the month.

Another unique characteristic of these cloud based services

is the ability to spin up a new server whenever

you might need it.

This is called on-demand self-service.

We can add a new server, a new network, or a new application

by clicking a few buttons.

We don't have to purchase a new server

or install it into the rack.

Instead, we can spin up a virtual system

in a matter of seconds.

This allows instant resource provisioning.

Somebody needs to have some services available,

we can configure our cloud based services

to make those services available in just a few moments.

One challenge, of deploying applications

is you have to wait for hardware or software or the network

to be available.

But with a cloud-based service, we have on-demand self-service.

We can click a few buttons and create a new server,

a new network, or new application

from these resources available in the cloud.

This is a process that is near instantaneous.

So we can click a few buttons and have

a brand new application deployed to our users very,

very quickly.

Cloud-based services also allow us to take

advantage of resource pooling.

Instead of purchasing many small servers

and having some of those servers sit idle,

we can instead purchase a very large piece of hardware,

and then virtualize all those servers

inside of that large hardware.

That way we're able to take advantage

of idle times with one server by using those resources

with another server.

Cloud-based services also allow us

to measure every aspect of that application.

We can see the bandwidth set in and out of the application.

We know exactly the storage that's

being used for that application.

We can measure how many people are using that application.

And then we can build based on all of those different metrics.

So if you wanted to know exactly how much it

was going to cost to be able to run a particular application,

you can measure every aspect of it

and have a very good idea of how much that application will

cost.