Study/Devops-exercises
1
0
Fork 0
mirror of https://github.com/bregman-arie/devops-exercises.git synced 2026-02-04 23:59:11 +00:00
Code Issues Packages Projects Releases Wiki Activity

add horizontal scaling and vertical scaling (#10468)

Browse Source 
* add horizontal scaling and vertical scaling

* fix: keep original formatting

* fix: keep original formatting

* fix block
This commit is contained in:
Reuben D'Souza 2024-08-31 04:14:00 -04:00 committed by GitHub
parent a23bb82cd7
commit 4efd1339f0
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
topics/cloud/README.md
View File

@ -91,6 +91,16 @@ AWS definition: "AWS Auto Scaling monitors your applications and automatically a
Read more about auto scaling [here](https://aws.amazon.com/autoscaling)
</b></details>
<details>
<summary>What is the difference between horizontal scaling and vertical scaling?</summary><br><b>
[AWS Docs](https://wa.aws.amazon.com/wellarchitected/2020-07-02T19-33-23/wat.concept.horizontal-scaling.en.html):
A "horizontally scalable" system is one that can increase capacity by adding more computers to the system. This is in contrast to a "vertically scalable" system, which is constrained to running its processes on only one computer; in such systems the only way to increase performance is to add more resources into one computer in the form of faster (or more) CPUs, memory or storage.
Horizontally scalable systems are oftentimes able to outperform vertically scalable systems by enabling parallel execution of workloads and distributing those across many different computers.
</b></details>
<details>
<summary>True or False? Auto Scaling is about adding resources (such as instances) and not about removing resource</summary><br><b>
@ -105,4 +115,4 @@ False. Auto scaling adjusts capacity and this can mean removing some resources b
* Instance should have minimal permissions needed. You don't want an instance-level incident to become an account-level incident
* Instances should be accessed through load balancers or bastion hosts. In other words, they should be off the internet (in a private subnet behind a NAT).
* Using latest OS images with your instances (or at least apply latest patches)
</b></details>
</b></details>