Css Web请求生命周期

今天晚些时候我有一次面试，我可能会被问到以下一个问题：

“描述从前端到中间/API到后端的请求的生命周期。每一步需要什么样的软件体系结构？”

---

这些我都不是很确定。有人能帮我把他们认为对这样一个问题很好的答案贴出来吗？谢谢。

我想架构就是这个问题中的软件

    1. The IP of mywebsite.com is resolved by a DNS request. 
    2. The DNS request is answered by the DNS server.
    3. A TCP/IP connection is opened to *.*.*.* 
       A http get/post request is issued to the server via HTTP
    4a) A firewall is passed (if present), and the request is hopefully forwarded to the web-server
    4b) The web-server receives the request, 
    and based on it's virtual hosting configuration information and the information in the http-headers, will forward the request to the respective application 
    via FastCGI or using a Server-Module/ISAPI.'
    5. The web-application receives the request for http://mywebsite.com/jobs/edit/1
    6a) HTTP-modules are executed for this request (e.g. forms authentication, banning)
    6b) If the route is registered in the routing regex, the request is routed to the appropriate MVC controller (jobs)
    7. The edit action in the MVC controller is called with parameter 1
    8. The edit view is returned for parameter 1
    9. The client receives the HTML
    10. the port is closed by the client & server

    "Describe the lifecyle of a request to http://mywebsite.com/jobs/edit/1 from front-end to middle/API to backend. 
    What kind of software architecture would be needed at each step?"

    1. Requires DNS-client
    2. Requires DNS-Server
    3. Requires web-browser or TCP/IP/HTTP capable application
    4. Requires web-server that is virtual name based hosting capable
    5. Requires a web-application, like PHP/ASP.NET/Python/Perl
    6-8. Requires MVC application architecture
    9-10. Stateless architecture

---

已经有一个很好的答案可能会有所帮助[这里][1][1]：关于软件体系结构的部分仅仅是您需要一个web服务器和一台客户机，以便能够使用TCP/IP协议通过HTTP进行通信吗？这是一个真正让我困惑的部分，它创造了另一个可能有助于这个问题未来观众的广泛答案：