1. Describe the Web-Request-Response-Cycle
The Web Request Response Cycle is the cycle between a client and a server. Clients send requests to the server, and the server sends requests back to the client. If there is a database involved, the server will sometimes become the client and send requests to the database, which then sends the response back to the server, and the server sends the response back to the client.
A user opens his browser, types in a URL, and presses Enter. When a user presses Enter, the browser makes a request for that URL. The request hits the Rails router (config/routes.rb). The router maps the URL to the correct controller and action to handle the request. The action receives the request and passes it on to the view. The view renders the page as HTML. The controller sends the HTML back to the browser. The page loads and the user sees it.
2. Explain what a “server” is, as it relates to the WRRC
A server is the thing that sends a response back to the client
The client (usually a browser) opens a connection to the server and sends a request. The server processes the request, generates a response, and closes the connection if it finds a Connection: Close header. … Headers are typically only sent for POST and PUT methods.
Web browsers communicate with web servers using the HyperText Transfer Protocol (HTTP).
3. What does it mean to “deploy” an application?
Deploying an application means you have pushed it up to a hosting site that can host your application.
Software deployment refers to the process of running an application on a server or device.
| Term | Definition |
|---|---|
| Server | Something sending a web response |
| Pub/Sub | In software architecture, publish–subscribe is a messaging pattern where senders of messages, called publishers, do not program the messages to be sent directly to specific receivers, called subscribers, but instead categorize published messages into classes without knowledge of which subscribers, if any, there may be. wiki |
| WRRC | Web Request Response Cycle. |
Which 3 things had you heard about previously and now have better clarity on? Elastic BeanStalk, AWS, WRRC
Which 3 things are you hoping to learn more about in the upcoming lecture/demo? AWS, the cloud, EC2
What are you most excited about trying to implement or see how it works? All things AWS!! So much to learn