Repos-que-me-gustan/devops-exercises
1
0
Fork 0
Code Pull Requests Activity

Update

Browse Source
This commit is contained in:
abregman 2022-05-24 20:09:48 +03:00
parent 218a43ee31
commit 05f055f0c0
2 changed files with 27 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
README.md
View File

@ -6595,10 +6595,6 @@ The server didn't receive a response from another server it communicates with in
<summary>What is a reverse proxy?</summary><br><b>
</b></details>
<details>
<summary>What is CDN?</summary><br><b>
</b></details>
<details>
<summary>When you publish a project, you usually publish it with a license. What types of licenses are you familiar with and which one do you prefer to use?</summary><br><b>
</b></details>
@ -7119,6 +7115,28 @@ Bonus: extract the last word of each line
<summary>Explain what is a "Single point of failure"?</summary><br><b>
</b></details>
<details>
<summary>What is CDN?</summary><br><b>
CDN (Content Delivery Network) responsible for distributing content geographically. Part of it, is what is known as edge locations, aka cache proxies, that allows users to get their content quickly due to cache features and geographical distribution.
</b></details>
<details>
<summary>Explain Multi-CDN</summary><br><b>
In single CDN, the whole content is originated from content delivery network.<br>
In multi-CDN, content is distributed across multiple different CDNs, each might be on a completely different provider/cloud.
</b></details>
<details>
<summary>What are the benefits of Multi-CDN over a single CDN?</summary><br><b>
* Resiliency: Relying on one CDN means no redundancy. With multiple CDNs you don't need to worry about your CDN being down
* Flexibility in Costs: Using one CDN enforces you to specific rates of that CDN. With multiple CDNs you can take into consideration using less expensive CDNs to deliver the content.
* Performance: With Multi-CDN there is bigger potential in choosing better locations which more close to the client asking the content
* Scale: With multiple CDNs, you can scale services to support more extreme conditions
</b></details>
<details>
<summary>Explain "3-Tier Architecture" (including pros and cons)</summary><br><b>
</b></details>

10
exercises/devops/README.md
View File

@ -3,21 +3,21 @@
<details>
<summary>What is DevOps?</summary><br><b>
You can answer it by describing what DevOps means to you and/or rely on how companies define it. I've put here a couple of examples.
The definition of DevOps from selected companies:
Amazon:
**Amazon**:
"DevOps is the combination of cultural philosophies, practices, and tools that increases an organization’s ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes. This speed enables organizations to better serve their customers and compete more effectively in the market."
Microsoft:
**Microsoft**:
"DevOps is the union of people, process, and products to enable continuous delivery of value to our end users. The contraction of “Dev” and “Ops” refers to replacing siloed Development and Operations to create multidisciplinary teams that now work together with shared and efficient practices and tools. Essential DevOps practices include agile planning, continuous integration, continuous delivery, and monitoring of applications."
Red Hat:
**Red Hat**:
"DevOps describes approaches to speeding up the processes by which an idea (like a new software feature, a request for enhancement, or a bug fix) goes from development to deployment in a production environment where it can provide value to the user. These approaches require that development teams and operations teams communicate frequently and approach their work with empathy for their teammates. Scalability and flexible provisioning are also necessary. With DevOps, those that need power the most, get it—through self service and automation. Developers, usually coding in a standard development environment, work closely with IT operations to speed software builds, tests, and releases—without sacrificing reliability."
Google:
**Google**:
"...The organizational and cultural movement that aims to increase software delivery velocity, improve service reliability, and build shared ownership among software stakeholders"
</b></details>