Skip to content

Latest commit

 

History

History
115 lines (69 loc) · 3.74 KB

File metadata and controls

115 lines (69 loc) · 3.74 KB

Learning Objectives

General

  • You must be able to draw a diagram covering the web stack you built with the sysadmin/devops track projects
  • You must be able to explain what each component is doing
  • You must be able to explain system redundancy
  • Know all the mentioned acronyms: LAMP, SPOF, QPS

Domain and Subdomain:


DNS:

  • The DNS, or Domain Name System, acts like a giant phonebook for the internet. It translates human-readable domain names (like "[invalid URL removed]") into numerical IP addresses (like 172.217.160.132) that computers use to connect to each other. Here's a breakdown of how it works:
  • Whenever u browse a specific website (google.com), the browser have to get it's IP address in order to browse it, so first the browser searches for the IP in it's cache, if not found then will search in the OS cache, if not found the DNS is starting to do it's role (
    • The OS will ask the resolver to got the IP of google.com, then the resolver will search in it's cache, if it's not found then the resolver will make a short trip to got it.
    • Resolver will ask the Root Server for it, but the Root Server will response with the Top Level Domain Server (TLD Server) [.com TLD Server, .org TLD Server ...] then TLD will response with the Authoritative name servers addresses, then the authoritative will reply with the IP address of google.com.
    • )
    • This interesting journey explained here: https://howdns.works/ep1/

Types of DNS Records:


Server:


Web Server:


Load Balancer:

  • It distribute the requests to multiple or several systems or servers.
  • Load balancers like (HAProxy, Nginx, ...) are using some algos to acheive it:
    • Weighted Scheduling Algo.
    • Round Robin Scheduling Algo.
    • Least Connection First Scheduling Algo.
  • For more details: https://www.thegeekstuff.com/2016/01/load-balancer-intro/

Web Server vs App Server:


SPoF (Single Point of Failure) :


High Availability :


How to avoid downtime when deploying new code :


HTTP vs HTTPS :


What is a firewall :