How the site works / What happens behind the scenes

I am trying to understand what happens in the background when using a website or basically what happens when a user interacts with a browser. I understand that this is a huge list and is highly dependent on architecture and user actions, etc., I'm just trying to understand the basic things and clear my misunderstandings, and also use this to learn more about things that I do not understand.

As an exercise, I am trying to point out things that happen in the background regarding user actions in the browser. Here is my attempt at this open but interesting question:

The user enters the browser url => if available in the browser cache => DNS look up [root dns lookup => recursive dns => get ip] => set tcp connection => send http req => get static page from the web server = > if authentication is required, which [reading a cookie from the browser OR asking the user to enter credentials] => somehow receives dynamic elements as well [like?, is there some kind of lazy initiative here?] => Then the user performs some action [clicks the link or something] => check the browser’s cache => if it doesn’t help [accept the input parameters and paste it in the URL in some way [maybe some things can be encrypted if necessary] => gets into the load balancer => aimed at application server [whicheverhow LB selects the host application] => the server’s cache is checked [memcached or some kind of caching, not sure if this "normally" happens here or at some other level] => the application server is trying to understand the request [if its service listening on some then port, http-port 80, it will get the URL and analyze the performance of some operations] => if necessary, the database is requested => mgmt connection / caching / parallel requests again, etc. here => returns the result to the application server => the application server the result of the payload and headers [http] => sends it to the browser for rendering => the browser cache is updated => the user responds to the answer.normal "happens here or at some other level] => the application server is trying to understand the request [if its service listening on some port, http port 80, it will get a URL and analyze the execution of some operations] => if necessary, the database is requested data => the connection may again be mgmt / caching / parallel requests, etc. here => returns the result to the application server => application server the result of the payload and headers [http] => sends it to the browser for rendering => browser cache updated => user responds to a response.normal "happens here or at some other level] => the application server is trying to understand the request [if its service listening on some port, http port 80, it will get a URL and analyze the execution of some operations] => if necessary, the database is requested data => the connection may again be mgmt / caching / parallel requests, etc. here => returns the result to the application server => application server the result of the payload and headers [http] => sends it to the browser for rendering => browser cache updated => user responds to a response.he will get a URL and analyze the execution of some operations] => if necessary, a database is requested => mgmt connection / caching / parallel requests, etc. can again be here => returns the result to the application server => the application server the result of the payload and headers [http] => sends it to the browser for rendering => the browser cache is updated => the user responds to the answer.he will get a URL and analyze the execution of some operations] => if necessary, a database is requested => mgmt connection / caching / parallel requests, etc. can again be here => returns the result to the application server => the application server the result of the payload and headers [http] => sends it to the browser for rendering => the browser cache is updated => the user responds to the answer.

/ , ,

:
, , - .. .. , !

• .
• , .
• , - .
• .., [ , ]

!