The Truth About Web Development

What comes to your mind when you hear someone say Web Development? Probably something along the lines of “designing” a webpage, right? Web Development and Web Design are two totally different areas, interesting in their own way. Web Development is so much more than just Web Design.

Let’s get technical.

Any webpage has three components:

  • Client: The local system that the user interacts with. (popularly called “User Interface”)
  • Server: The remote computer that hosts all the files that make up the website.
  • Database: Technically a part of the server, a database is a large series of data tables, used to store all the dynamic information generated or used within the website.

The basic flow of a webpage is very simple to understand.

The user first enters the URL of the website (let’s say www.facebook.com) on his/her local computer (the client).

The user’s computer generates a “request” that is sent to the server computer which then accepts the request.

The server runs the back-end code while taking data from the database.

The database then sends the requested data back to the server.

The server takes the data and executes the front-end code to produce a “response”. This “response” is sent back to the client where it is displayed (or rendered) on the client computer as a web page.

So there are clearly two sides of development:

  • The Front End: A front-end developer is the one who builds the interface, and provides the layout as the interaction between the back-end of the website and the user.
  • The Back End: Back-end developers are those who control the server data and requests.

Full Stack Web Developers are those who work on both front-end and back-end code.

Getting back to words like “response” and “request” mentioned above. HTTP stands for Hypertext Transfer Protocol. It’s an application-layer protocol for communicating between distributed systems. HTTP basically is a protocol to facilitate communication between hosts and clients.

Communication between a host and a client occurs, via a request/response pair. The client initiates an HTTP request message, which is serviced through an HTTP response message in return. How is the request message sent? They are sent via Uniform Resource Locators (URLs). I’m sure you are already familiar with URLs.

The protocol is typically http, but it can also be https for secure communications. The directory is the local path to the resource on the server.

So how much of “Web Design” did I talk about? Hardly anything, right? A million processes (only some of which I mentioned), go on behind the scenes during the load of a webpage that go overlooked.

There is so much more to Web Development than Web Design.

– Nishanth Subramanian

 

Leave a Reply

Your email address will not be published. Required fields are marked *