Notes
AWS - What Is Cloud Computing? #Chapter1 - Criado a partir de um Mapa Mental
Content of the notes (1)
Page 1
Using a public cloud is about using other people's servers to run your digital workloads.
In a sense, there's no significant difference between running a software application on servers hosted in your own office versus locating it within Amazon's infrastructure. In both cases, you need to make sure you've got sufficient compute, memory, network, and storage resources. In both cases, fast deployments and avoiding overprovisioning are key goals.
But particularly when it comes to the largest cloud providers, there are important differences. You see, the sheer size of a platform like AWS (and right now there's no platform on Earth that's bigger) means it can offer you service, cost, and reliability performance that you could probably never hope to re-create on your own.
Highly Available and Scalable Resources
There's an awful lot a successful company like AWS can get done with a few hundred thousand networked servers and hundreds of the best trained engineers in the business:
Design multiple layers of redundancy so that whenever one component fails, its workload is automatically and instantly moved to a healthy replacement. This is often known as “failover.”Connect resources in geographically remote locations so that the failure of one complete region could trigger a predefined relocation of resources. This relocation can be supported by a similarly automated rerouting of network requests.Provide customers with access to as much compute power as they could possibly need and deliver that power on-demand.Because of the scale and efficiency of the platform, AWS can do all that at a price that's often far below what it would cost you to run comparable workloads locally.
Professionally Secured Infrastructure
IT security is a constantly moving target. As difficult as it's been to manage last year's threats, you know there's a whole new batch coming right behind them. As a business, you're already responsible for protecting the workstations and networking hardware running in your office along with securing your organization's data and code your developers put into your apps. The integrity of your underlying server infrastructure is just one more potential area of vulnerability for you to worry about.
No matter how good your IT security team is, they're probably not better informed, equipped, and trained than their counterparts at a major cloud provider. Because AWS is so good at what it does—and because it takes responsibility for the security of its platform's underlying networking and compute infrastructure—this is one area where outsourcing will usually make sense.
Metered Payment Model
One of the defining characteristics of any public cloud computing platform is the way it automatically allocates resources to meet client requests. Practically, this means that you can, for instance, log in to the AWS browser console and define and launch a virtual server (called an instance in the AWS world), and moments later your new instance will be ready for you. There's no need to wait for manual intervention by AWS employees.
The flexibility of the self-serve system permits usage patterns that would have been impossible using traditional compute paradigms. Let's say you need to quickly test a possible application configuration you're working on. In the old days, even if the test lasted only an hour, you would still need to find free capacity on a physical server in the server room. Once the test ended, you'd still be paying the maintenance and ownership costs of that server capacity even if it was idle.
Server Virtualization: The Basics
The secret sauce that lets cloud providers give their customers on-demand compute resources in such a wide range of configurations is virtualization. When you request a virtual machine (VM) with a particular processor speed, memory capacity, and storage size, AWS doesn't send some poor engineer running through the halls of its data center looking for an available machine with exactly that profile. Rather, as you can see illustrated in Figure 1.1, AWS carves the necessary resources from larger existing devices.
virtualization model two compelling benefits
Amazon's formidable scale and logistical abilities mean that it's often able to leverage the benefits of virtualization to provide both superior performance and pricing.
Cloud Platform Models
Serverless Workloads
Besides doing an excellent job emulating traditional server behavior, cloud providers can also enable entirely new ways to administer applications and data. Perhaps the most obvious example is serverless computing.
Now don't be fooled by the name. You can't run a compute function without a computer environment (a “server”) somewhere that will host it. What “serverless” does allow is for individual developers to run their code for seconds or minutes at a time on someone else's cloud servers.
The serverless model—as provided by services like AWS Lambda—makes it possible to design code that reacts to external events. When, for instance, a video file is uploaded to a repository (like an AWS S3 bucket or even an on-premises FTP site), it can trigger a Lambda function that will convert the file to a new video format. There's no need to maintain and pay for an actual instance running 24/7, just for the moments your code is actually running. And there's no administration overhead to worry about.
Scalability and Elasticity
capital expenses (CapEx)
operating expenses (OpEx)
Speed
Defining, purchasing, provisioning, testing, and launching a new physical server can take months. Even a simple reboot can keep you waiting for a couple of minutes. The time lag between requesting a new cloud-based VM and logging in and getting to work can be seconds, but never more than a few minutes. Restarting a VM can sometimes happen faster than you can type your login details
Efficiency
It's rare to find a nonvirtualized physical server that utilizes anywhere near 100 percent of its capacity. More likely, either it will spend its time running mostly empty or it will be badly overused while you wait for more capacity to come online. Multiple virtual machines, on the other hand, can be tightly packed onto a physical server running a hypervisor (a common technology for hosting VMs). When space opens up on one server, you can quickly fill it with another virtual workload. When a server reaches capacity, overflow workloads can be moved to another machine. And the more workloads you're managing, the more flexible everything gets.
Infrastructure as a Service
Infrastructure as a service (IaaS) products generally simulate the look and feel you'd get from managing physical resources. IaaS products give you direct access to a provider's compute, storage, and networking assets. Because it's you that's in there playing around at the hardware level, you—rather than the IaaS provider—are responsible for the consequences of any bad configurations. The trade-off is that you get to closely configure every layer of your operating stack.
You'll learn much more about these examples later in the book, but AWS IaaS products include Elastic Cloud Compute (EC2) for virtual machine instances, Elastic Block Store (EBS) for storage volumes, and Elastic Load Balancing.
Platform as a Service
Unlike IaaS, platform as a service (PaaS) products simplify the process of building an application by hiding the complexity of the infrastructure that runs it. You're given an interface through which you define the behavior and environment you want for your application. This will often include the code that will run your application.
AWS PaaS products include Elastic Beanstalk and Elastic Container Service (ECS).
Software as a Service
Software as a service (SaaS) products offer services meant to be accessed by end users. An easily recognizable illustration is Google's Gmail service, which allows users to manage their email by logging in to a browser interface or through an email client (like Microsoft Outlook) that's running locally.
While some may disagree with the designation, AWS SaaS products arguably include Simple Email Service and Amazon WorkSpaces.
Scalability
Elasticity
You can stretch an elastic band far beyond its resting state. But part of what makes it truly elastic is the fact that, when you let go of it, it immediately returns to its original size. The reason the word elastic is used in the names of so many AWS services (Elastic Compute Cloud, Elastic Load Balancing, Elastic Beanstalk, and so on) is because those services are built to be easily and automatically resized.
Generally, you set the maximum and minimum performance levels you want for your application, and the AWS service(s) you're using will automatically add or remove resources to meet changing usage demands. By way of illustration, a scalable e-commerce website could be configured to function using just a single server during low-demand periods, but any number of additional servers could be automatically brought online as demand spikes. When demand drops back down, unused servers will be shut down automatically.
Information
- Description
- Profissionalizante AWS Note on AWS - What Is Cloud Computing? #Chapter1 - Criado a partir de um Mapa Mental, created by Luiz Eduardo on 23/07/2025.
- Created by
- Luiz Eduardo
- Views
- 5
- History
-
- Created by Luiz Eduardo · Jul 23, 2025
- Copied to Note by Luiz Eduardo · Jul 23, 2025
- Rating