7 hours 31 minutes
Hello and welcome back to Cloud architecture foundations. This is module to cloud characteristics, and before we go deep in the Amazon Web service is Microsoft Azure and Google Cloud Platform.
We need to get our arms around some of the characteristics that are unique to the cloud but common to the cloud providers that we n i t are going to support.
Cloud characteristics is all about the terminology and the technology that is needed for us, and I t. To be able to design, migrate, develop, utilized, optimized, troubleshoot and support. Our cloud service is our cloud applications, and what's most important are in user community.
So some of the unique clown characteristics that we're going to cover in module to our elasticity cloud bursting pay as you grow
chargeback, ubiquitous access, multi tendency and demand driven service's and much, much more.
If you've ever played incredibly flashed and incredibly awesome paintball, you know you're gonna do a few things to stay alive. You gotta duck and cover to stay out of harm's Ray and then to hurry and get back on the offensive. You gotta tuck and roll well in module to we're gonna do a lot of our own tuck and roll.
We're going to review a term, and then we're gonna learn about that term using a use case, and they were gonna roll into the next term.
So if you're ready, let's tuck and roll.
So to start with, let's compare and contrast cloud elasticity with cloud scalability. Cloud elasticity in the world of computing. It's a service, for example, is like computing is a service without limits. Elasticity is like having an unlimited tape drive where you can continue to store information as your needs. Change
in cloud computing elasticity means that your organization can dynamically provisions and stand up computer processing,
memory and storage to meet the needs of your organization.
Elasticity is just one of the many benefits of cloud computing because it allows your organization to gain capacity without having to build up the compute and storage resource is within your own data closets and within within your own data centers. Cloud scalability, on the other hand, is, for example,
when the host has been provisioned with your computers of service with its compute
memory and storage resources is only currently a 50% utilization.
Thus your host could have additional virtual machines turned up until you are closer to capacity.
So elasticity is the ability of a system to increase its workload by adding hardware. Resource is, while scale ability is the ability of a system to increase its workload on, they're currently provisions. Hardware resource is
so a good example of the clouds. Rapid elasticity is when our organization needs to take advantage of the clouds computers of service. So the cloud provides our organization a host and we stand up a new operating system for the new application we're developing. And when our application is built, we need to move from testing to prototype
and customer pilot testing while we're in the scrum agile software development Life cycle.
But we under provisions are development environment to serve as a customer piloting testbed. Our lab environment was built with the capability to only have a handful of our developers on box and then the system at any one time. We built the lab environment small to start with because we didn't know how long it was going to take us to develop the app
what hurdles and challenges we might have to overcome.
So we built the test of environment small to save cost. But we are ahead of schedule. We're ready to go right to customer testing, and we don't want to rebuild the environment on a bigger server just to handle the capacity of all the users we need to support for the customer pilot phase. So a cloud elasticity We simply ADM or processor and memory to our environment
almost immediately and now a testing environment, which was previously only for a few users,
can now support the 500 users in the customer testing environment. And when we have finished our two week customer pilot weaken, wind back down,
we could turn our processor memory use back down to a small environment again. So we go back to coding and fixing our software with the bugs we identified through our customer testing and we, with the elegance of the cloud and cloud elasticity scaled up and then back down quickly, and we only have to pay for the resource. Is we used while we use thumb,
rather than if this environment was premise based, we would have built up a small test of environment and then a much bigger customer testing environment with the cloud and cloud elasticity. We scaled up and down when we needed it and saved a ton of cost and effort. Having to stand up multiple use case systems in our own environment. Really, really
So you might remember for module one when we said the computer hardware, software and storage virtual ization is what makes the cloud possible. Well, we are looking at a screen shot on the left of several computer hosts. Servers that are running Veum wher E s X I virtual is ations operating system and software,
and you will see that each of the computers is only using a small part of their computing and memory capacity.
The screen shot on the right shows a del powered server with four CPU cores and cores a processor. This computer has four processors and 32 gigabytes of random access memory, or RAM. So this del box on the right can run four processors at three gigahertz processing performance each
Warrick and perform 12 gigahertz of CPU processing minus the overhead
and utilize 32 gigabytes of memory. You can see the blue scale bars and the screenshot that shows you can turn on more resource is that might require CPU compute, but there's not much more memory left that's available. Scalability in the cloud means that if we use the left screen shot as an example that we're paying for and using five hosts in the cloud.
But we have a lot more capacity or scalability
to provisioned more virtual machines, virtual servers and virtual computers. We will talk a lot more about computer hardware and software virtual ization in a later cloud. Architecture Foundations module For now,
I understand the clown's scalability means you're only partly using. The resource is your organization is paying for and you can turn on. New service is as your business demands with using the cloud and virtual ization technology.
So in our previous example, we talked about a software development team that need to scale up to go to customer testing and then scale back down. This is where the clouds pays. You go and pays. You grow. Billing principles really stand out. One of the advantages of of the public cloud is the pains you grow charging Model allows your organization to pay for service is by the hour
or based on the compute resource is it uses.
You don't have to pay a large upfront investment to start with Cloud Infrastructure Service's. And then as you go and grow, you only have to pay for what you use. Most cloud providers have calculators and other pricing tools that can help your organization develop its own pricing models up front.
Shorten long term to develop, return on investment indices and maximize your R O. I may be paying a little bit more upfront, reduces your hourly and long term use costs. Or maybe starting off with less even though you will pay. A higher use rate is worth the risk to the organization because you really just don't know what the future will bring.
The pay as you go and page group building models of the cloud
can really save an organization. A procurement cost deployment costs an ongoing management costs of compute memory and storage infrastructure that they only partially use or using burst. He starts and stops Premise based infrastructure investment has a lot of challenges.
The clouds pays you go and pays your use. Consumption model can really appease the appetites of today's small to medium businesses.
SMB midmarket and today's enterprise
Oh No, you cloudy chimpanzees. It's time for that learning check.
What is quite elasticity
was the difference between cloud elasticity and cloud scalability.
And how does the cloud pays You go grow building model help of cloud adoption.
So hit pause Have a banana come up with your answers and then hit plane will review our answers together.
Welcome back, you cloud climbing chimpanzees So what you come up with for what is cloud elasticity? If you said the last city is like having unlimited resource is and you just add cloud resource is as you need them and pay for what you use Well, you get 100% partial credit Cloud elasticity is also why your cloud bill stretched to such a giant number
because you failed to use your cloud providers payment calculator when you signed up.
Seriously, when you pay by the hour and don't figure it out up front well, it can get really expensive really fast So get out that calculator ad buy to divide by pi multiplied by the speed of light and then maybe if you can afford it Elasticity is for you. Elasticity allows you to add resource is
scalability allows you to scale out by fully utilizing what you already are paying for
and are already provisioned for and pay by the hour. If that helps your up and down. The last two cloudy service pay for only what you use is an amazing differentiator to premise based. Build it first and they will come approach.
So in today's lecture, we spent some time talking about the up and down yo goes of business. Now organizations can really benefit from the clouds elasticity model.
The cloud allows us to fully scale out and use what we're already paying for before we need to buy more stuff. Try that with your on premise approach to compute and storage, where oftentimes I t is asked to build of infrastructure for future capacity. And then the company will follow maybe and pays you use. Modeling can make a real difference depending on how you use it.
And if you were always on the lookout for what could be a cloud creeping bill
for your service is so next time will be looking at the cloud characteristics of chargebacks, metering and it really fun to say, cloud bursting cloud capability.
So there's guys like this That probably don't care. But on behalf of the entire cyber ery security and I t Learning team, we wanna wish you and all the users on your network very happy packets.