These are my reading notes for Code Fellows
First a user gives a client a URL, the client builds a request for information (or resources) to be generated by a server. When the server receives that request, it uses the information included in the request to build a response that contains the requested information. Once built, that response is sent back to the client in the requested format, to be rendered to the user. (source)
The requester is the client and the responder is the server.
A deployed application is hosted on a server (Heroku, Netlify, AWS) and accessible by other machines, non-locally.
Computer processes that provide application services are referred to as servers, and create sockets on startup that are in the listening state. (source)
…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. Similarly, subscribers express interest in one or more classes and only receive messages that are of interest, without knowledge of which publishers, if any, there are. (source)
Web Request Response Cycle. A user might send a request and get a response from a server. WRRC describes that relationship.