In this video, we will finish up section 2 and discuss the four
deployment models.
Depending on your requirements and business your cloud computing
needs may require a very simple architecture or more
complex one.
The key to the cloud is its flexibility to work for you with choice
and efficiency.
Today there are four common cloud computing deployment models called
public private hybrid and
multi.
Each one has its purpose and will be up to you
to choose one that fits your environment. Let's talk about each of
them in more detail.
The first model is Public public Cloud
basically means that all the resources and services are available over
the internet you the user is just paying
for what you need and do not have ownership of the infrastructure or
Services. The public cloud is the most common and
what you will probably use when you decide to move your workload
there.
This model is your best choice when starting out and
are on a budget.
The second model is private. This is the opposite of public
you have your own slice of the cloud and do
not share with anyone. This means you most likely own the
infrastructure and have a high level of access to it. You
should choose this when you need more control and privacy in
your environment the cost for this model is high compared to
the public one.
Third model is hybrid. This is where you
blend the first two models public and private into one
Cloud Nirvana. You can store sensitive information in your
private cloud while serving it up through the public one. Usually
this is done with a direct link or site to site
VPN between the two models.
This option is great. If you need more privacy and control on
some portions of your architecture, but would like to take advantage
of the public Cloud cost savings and efficiency.
The fourth model is multi-cloud. This model is becoming
more and more popular as companies want to ensure availability and
avoid Cloud vendor lock-in the multi-cloud
model not that different from hybrid uses two
Cloud providers to either split the workload between them or
put one piece of your infrastructure on one and
another on the other.
For example, you could run a web service on AWS cloudfront while
serving the backend database on bigquery inside of
Google Cloud. You should choose this model if
your data or Services sensitive to outages or you
find your architecture favors One Cloud providers product
over another
for our recap. I wanted to discuss some of the drawbacks of
these models instead of just reciting the purposes over again
public which is what you use in the next
section when we create our lab it sacrifices control in
some security for convenience in ease of use
The private model while offering the most control is
the costliest option as you must own and operate your
own infrastructure.
The hybrid model can have increased latency between the private and
public Cloud. It can also prove to be difficult to
scale and manage as there are two different infrastructures you need to deal with
the multi-cloud model can be complicated to manage and
secure. It can also require extra costs
as you're running in two different Cloud providers, but like
I stated earlier this is
up to you to choose which deployment model fits your needs the best.
We have completed overview of devops and
cloud computing section.
As with all material in this course, I challenge you
to dig further by finding other information about devops and
cloud computing.
In the next section, we will be Hands-On setting up our Linux
server on AWS.