Well, as an upcoming Full Stack Developer, understanding how Internet works is very important.
I spent half month to watch Meteor's tutorial. It made me understand how Internet works. One of the intuitions for Meteor's developers develop Meteor is that they don't like HTTP Protocol, which I will explain it shortly. Therefore, Meteor is using DDP Protocol, Distributed Data Protocol.
We have been using HTTP Protocol since 1991. So, what is HTTP Protocol? So, we have three people, one is Client, one is Medium, and the other one is Server.
Client is submitting "What is your name?" to Server. So, the Medium is passing this question to Server. After Server received the question, it is looking for answer within the files it has. When Server got the answer after computation, it will send the "answer" back to the Client, and the Medium is passing the "answer" to Client. In this whole process, we complete one single request. So, whenever, the Client submits a request to Server, it has to go through this whole process every single time.
However, it real life, there are so many clients in the middle of you and the server. Our requests for the server will go through several clients, and they are being the Medium position to pass our requests to the Server. If our requests were dead in the middle, our sysmem will detect it and resend the requests again.
If you are interested in what DDP is and how does DDP work? You can check out Meteor's website.