This post is part of a resource called Developer Dictionary. More about why I'm writing this here
Client, server, frontend, backend, fullstack, request, response, website, web application — all of these terms are used very frequently in the world of web development. And if you're been learning programming for the web, even few weeks, you've probably been exposed to these terms. Here I illustrate what these words mean so you have a clear picture of the concepts behind the words and how they relate to the structure of the web.
What is the Client Server Pattern?
We can think of a server as a computer that holds data related to our website and code that reads/writes that data. A client is another computer that has a browser — a program capable of running code on behalf of the user (usually Javascript code) and making requests to the server. Server awaits and responds to client requests. One server serves many clients.
The same client could communicate with multiple servers. And the same computer can act both a s client and as a server. These are roles played with the computer based on the context. For example, when you're programming locally and you run a server on your computer and your browswer acts as the client (If you're ever typed localhost in your broswer you know what I mean). Continue Reading
Top comments (0)