If everything is a text document, how is it possible to have websites so amazing like Facebook, Youtube, etc?
Today’s websites are very different than before; they don’t have the same elements, but if we go back a bit in the past and explore the beginning of the Internet, it will all make sense.
The Internet was created for exchanging information. Its founders were looking for ways to share documents without having to rely on a complex infrastructure. They needed a framework and technology so that each person who wished to share a document could publish it independently and invite others to read it.
The scientific community started using it for the famous “Peer Reviews”, which required 3 colleagues to review and approve publications before they were accepted and published for all of the community to see.
For this reason, they worked on something as similar as possible to a Microsoft Word document or any other word processor.
The easiest way to think of the Internet is as a network of shared documents that were once rigid, formal scientific publications and, nowadays, are interactive, exciting and spectacular.
As it is to be expected, if you wish to share documents, all you need is text. When you build web pages, everything runs under the HTTP protocol (The Hypertext Transfer Protocol) which is a specialist in text transmission.
What this means is that: everything is text. For example, if you wish to send a photograph to your grandmother through an email, this is more or less what happens:
Image 1: The 4 steps needed to send images over the internet: first it turns to text, then it travels, then it arrives at grandma's computer, grandma opens the picture and the picture shows… lastly, grandma is happy looking at her grandson's photo!
Everything is connected. The best way to understand this is by comparing it to the postal service:
2 min video explaining how the internet works.
Remember how we said servers are the building lots? Well, to host a website, servers must meet all the requirements necessary so that the web pages won’t crash (just like the building lots).
Websites reside on servers. When users want to visit websites, they must enter the URL address in their browser. This will take them to the lobby or entrance of the web page (which is called the “index.html”).
Imagine that browsers are vehicles able to drive through the highways of the Internet, taking you anywhere!
If you’ve been reading and have understood everything so far, you must be wondering:
Well, browsers are equipped with "magical" windows. If you see through those windows you will see the world as it is: No Text!! The browser must perform all the functions that all other applications in your computer will accomplish. Like representing images, videos, text, sounds, etc., the browser is so great that there are even computers – like the Google Chromecast – that only come with a browser.
📺 Click here to access a video that explains how a Google Chrome Book works.
As you browse the Internet, the browser must translate every text it finds along the way while transforming the text into web pages with titles, subtitles, text, images, etc.
As a developer, you need to code everything the browser is going to need to visualize the text. We call it “the client side” because the browser is installed on the computer of the user. Likewise, all code on the client side will be processed by that computer.
The server has no idea of what the browser does! (Or at least it didn’t at the beginning (several years ago), and actually, it still doesn’t really know).
So, what does the server do?
Well, it does a lot! The server is responsible for preparing the text that will be read by the browser. The three major challenges for the server are:
|The Server||The Client|
|The server’s mission is to deliver all the text/information the client needs to render the website properly. It has a close relationship with the database (which manages and processes the data). It handles a high volume of information and is prepared to answer thousands of clients requests at the same time.|
The most frequent languages used are PHP, Python, Ruby and Java.
Little by little, the server has come to delegate part of its load. It handles fewer things now than before, but the ones it still handles are repeated many times. There are even services like Parse.com or Firebase.com that have created tools that allow developers to create web apps without even using their own server.
All the code that runs on the side of the server is called “The Back-End.” Back-End developers must strengthen their knowledge in databases, Bid Data, Data Mining, Security, Web Sockets, Web Services, API’s, etc.
Originally, the code that resided in the client didn’t do much because the documents were very simple. But things have changed; technology has given more relevance to the client to a point in which today there are thousands of apps that have more code on the client’s side than on the server side.
Running the code on the client side frees load off the server. After all, there is ONLY ONE server per THOUSANDS of clients.
All code on the side of the client is called “The Front-End.”
The most efficient way to learn: Join a cohort with classmates like yourself, live streamings, coding jam sessions, live mentorships with real experts and keep the motivation.
From zero to getting paid as a developer, learn the skills of the present and future. Boost your professional career and get hired by a tech company.
Start a career in data science and analytics. A hands-on approach with interactive exercises, chat support, and access to mentorships.
Keep your motivation with this 30 day challenge. Join hundreds of other developers coding a little every day.
Start with Python and Data Science, Machine Learning, Deep Learning and maintaining a production environment in A.I.