An HTTP request DNS domain name resolution--Initiates TCP three handshake--initiates an HTTP request after TCP connection is established--the server responds to the HTTP request, the browser gets the HTML code--and the browser parses the HTML code, and request the resources in the HTML code (such as JS, CSS, pictures, etc.)-the browser renders the page to the user
Design a storage system that stores massive amounts of data: Design a logical layer called "middle tier", in this layer, the database of massive data capture, make cache, run in the memory of the server, similarly, when there is new data to come, also first to cache, and then try to persist into the database, this is a simple idea. The main step is load balancing, distributing requests from different users to different processing nodes, and then caching them to update the data to the primary database at timed intervals. The process of reading and writing uses a mechanism similar to optimistic locking, which can be read all the time (while writing the data), but there will be a version tag each time it is read, and if the read version is lower than the cached version, the data will be re-read, which is not a lot to endure.
Links: The difference between HTTP and HTTPS
Links: Why is HTTPS more secure, first look at these
Links: HTTP request messages and HTTP response messages
Links: HTTP Request mode: Get and post comparison
Http and HTTPS