Breaking Down Web Jargon: Simplifying Common Terms for Beginners

Networking and the internet can often seem overwhelming because of the many technical terms used. But don’t worry! This blog is here to explain some of the most common terms in networking in a simple and engaging way. We’ll break down the jargon, so you don’t feel lost in a sea of complicated words. By the end of this blog, you'll be confident enough to explain these concepts to others, even if you’re just getting started.

Protocol

Protocols are like rules that help computers talk to each other. Imagine a postman delivering letters: for the postman to deliver letters correctly, there are rules he must follow, such as the correct address, where to drop off the letter, and how to ensure it reaches the right person.

In the same way, protocols provide the "rules" that computers follow to send and receive information. These rules make sure the message gets to the right place, in the right format, and in the right order. Without these rules, computers wouldn't understand each other, and communication wouldn't be successful.

There are different types of protocols that are used in computers; some of them are:

HTTP: Used for accessing websites.
FTP: Used to transfer files between computers.
SMTP: Used to send emails from one server to another.

Without protocols like HTTP, FTP, or SMTP, communication wouldn't happen between computers!

Request-Response Model

The request-response model is like a conversation between you and a shopkeeper. Imagine you're standing in front of a shop, and you want to buy a product. First, you ask the shopkeeper for the product you want (this is your request). After hearing your request, the shopkeeper goes to the shelf, picks up the product, and hands it over to you (this is the response).

In the same way, when you visit a website, your computer makes a request for information, like asking for a webpage. The server (which is like the shopkeeper) receives your request, finds the right data (the webpage), and then sends it back to you as a response, so you can see the webpage on your screen.

HTTP Headers and Payload

Header:

Imagine you're sending a letter to a friend. Along with the letter, you also include some information on the envelope, like who the letter is from, who it's going to, the date, etc. This information on the envelope helps the postman understand where the letter is going and if there’s anything special about it.

In the same way, HTTP headers are like the envelope in a web request. They contain extra information about the request or response, such as who is sending the message (the server or the browser), what kind of data is being sent, and other metadata. The headers ensure that the server and the browser understand how to handle the message.

Payload:

Now, the letter itself is what you actually want to send to your friend. The contents of the letter — the message you wrote — are the most important part. This part is like the HTTP payload.

The payload in HTTP refers to the actual data you want to send. For example, if you’re filling out a form on a website, the data you input, like your name or email, is sent in the HTTP payload.

Stateless Protocol

A stateless protocol is like a situation where each time you interact, it's as if you're starting from scratch, with no memory of what happened before. Imagine going to a store, making a purchase, and then leaving. The next time you visit, the cashier doesn’t remember that you bought something before unless you tell them. Each visit is treated as if it's the first time you're there.

HTTP (Hypertext Transfer Protocol) is stateless, meaning every time you visit a webpage, it's like starting fresh with no memory of previous visits. The web server doesn't recall anything unless you provide details, like logging in. It doesn’t know who you are or what you did before.
Why is HTTP Stateless?
HTTP is designed this way for simplicity and efficiency. By not tracking past interactions, it can handle more requests quickly without storing extra information. This helps keep the process fast and smooth each time you visit a page.

HTTP/2

HTTP/2 is like upgrading your old road to a new highway. Imagine you're driving on a single-lane road. If there are many cars, they all have to wait one by one, which makes the trip slow.

Now, think of a multi-lane highway. Many cars can drive at the same time, so they don’t have to wait in line, and the trip is much faster.

HTTP/1.1 vs HTTP/2:
- HTTP/1.1 is like the single-lane road. It sends one request at a time, which can take longer.
- HTTP/2 is like the multi-lane highway. It can send multiple requests at the same time, making everything faster.
  So, HTTP/2 helps data travel faster by sending many things at once, just like a busy highway!

TLS (Transport Layer Security)

TLS (Transport Layer Security) is like a security guard that makes sure your communication is private and safe. Imagine you want to send a message to a friend, but you don’t want anyone else to read it. So, you put the message inside a locked box and give the key only to your friend, ensuring only they can open and read it.

TLS in Action (HTTPS): When you see https:// in a website's URL, it means the communication between you and the website is protected by TLS. Just like the locked box, TLS ensures that any data you send or receive is encrypted and cannot be seen by others.
HTTP vs HTTPS: HTTP is like sending a postcard with your message written on it, so everyone who handles it can read it. On the other hand, HTTPS is like sending a letter in a sealed envelope, which only the recipient can open and read. This way, your message is private and secure.

SSL (Secure Sockets Layer)

SSL (Secure Sockets Layer) is like an old but trusted lock that protects your data during transfer, just like a locked box keeps a letter safe from being opened while it’s on its way. SSL was used to ensure that online communication, like passwords or personal details, couldn’t be read by anyone else. It’s now replaced by TLS (Transport Layer Security), a stronger, newer lock to keep your data even safer.

Session

A session is like a conversation between you and a website that happens while you're browsing it. Imagine you're having a chat with a friend: as long as you're talking, your friend remembers what you've said and can respond accordingly. For example, if you tell your friend that you're hungry, they'll remember that while you're talking, and offer suggestions for food later in the conversation.

Similarly, a session helps websites "remember" who you are while you're visiting. For instance, if you're logged into an online store, the website remembers your username, what items you've added to your cart, and your preferences during your visit. When you leave and come back later, the website knows who you are and keeps everything in place without needing you to log in again. Just like a conversation, the session lasts as long as you're interacting with the site. Once you leave, the session ends, and the website "forgets" your details.

A cookie is like a note that a website gives you to remember things about your visit. Imagine you visit a friend's house and they write down a note with your preferences, like your favorite drink or how you like to sit on the couch. The next time you visit, they can use the note to make you feel more comfortable right away, without you having to remind them.

In the same way, cookies are small pieces of information that websites store on your computer or phone. These notes help websites remember things like your login details, language preferences, or items you've added to your shopping cart. So, when you visit the website again, it can "read" the cookie and know things about you, making your experience quicker and easier. Just like a note, cookies are kept for a certain time, and when they expire, the website forgets the information.

Cache

A cache is like a shortcut or a memory that helps websites load faster the next time you visit. Imagine you're always going to the same friend's house. At first, it might take a while because your friend has to gather everything you need. But over time, they start keeping your favorite snacks and drinks ready, so when you arrive, everything is already there and waiting for you.

In the same way, a cache stores certain parts of a website (like images, files, or text) on your device. The next time you visit that website, your device can quickly "fetch" these saved items from the cache instead of downloading everything from scratch. This helps the website load much faster.

User Agent

A user agent is like an ID card that you show when you enter a place. Just like how your ID card tells someone your name, age, and other details, your user agent tells websites information about the device or browser you're using. For example, when you visit a website, your browser sends this "ID card" to the website, letting it know if you're using a phone, tablet, or computer, and which browser (like Chrome, Firefox, or Safari) you're using.

This helps the website customize how it shows up on your device. Just like a shopkeeper might offer you a different service if you show an ID card that says you're a member, the website can adjust its layout or features based on the information from your user agent. Here’s a properly formatted version of your note with bold and italics where needed:

TCP (Transmission Control Protocol)

TCP (Transmission Control Protocol) is like sending a letter with a return receipt to make sure the person who receives it confirms they got it. Just like when you send a letter, you want to know that it reached the right person and that they understood it correctly. TCP makes sure that the data sent between computers is delivered accurately, in the right order. If any part of the data is lost, it will be resent until everything is delivered properly. This ensures a smooth browsing experience, with all the website content appearing as it should.

3-Way Handshake (Connection Setup): Before sending data, TCP establishes a connection with a "handshake," like shaking hands to ensure both sides are ready to communicate. First, the sender asks if the receiver is ready, the receiver agrees, and then the sender confirms, starting the data transfer.

UDP (User Datagram Protocol)

UDP (User Datagram Protocol) is like sending a letter without waiting for a return receipt. When you send data, you don’t expect a confirmation that it was received. It’s faster, but there’s no guarantee that the data will reach its destination or be in the correct order.

No Connection Setup: Unlike TCP, UDP doesn’t do a handshake before sending data. It simply sends the data, like dropping a letter in the mailbox without checking if the receiver is ready or even if they get it.

Firewall

A firewall is like a security guard at the entrance of a building, deciding who can come in and who has to stay out. Just like a security guard checks the ID of each person entering and makes sure they are allowed inside, a firewall checks the data coming into or leaving a computer network. It looks at the "ID" (information about the data) and decides whether it's safe or might cause harm.

IP (Internet Protocol)

Think of IP (Internet Protocol) like the address on a letter that tells the postman where to deliver it. Just like every house has a unique address so that mail can be delivered to the right place, every device on the internet (like a computer, phone, or tablet) has a unique IP address.

URL (Uniform Resource Locator)

URL (Uniform Resource Locator) is like the address on a letter that tells the postman exactly where to go to deliver it, but in this case, it’s the exact location of a webpage on the internet.

When you want to visit a website, you type a URL into the browser, such as "www.example.com." Just like how you use a house address to find someone's home, the URL helps your computer find the exact webpage you want to visit. It’s a unique "address" for websites, telling your browser exactly where to go to get the information or the page you want, whether it's a picture, a blog, or a shopping site.

DNS (Domain Name System)

DNS (Domain Name System) is like a phonebook that helps you find the phone number of a person by looking up their name. When you want to call someone, you don't remember their long phone number; you just look up their name in the phonebook, and the phonebook gives you the correct number.

Similarly, when you want to visit a website like google.com, your computer doesn’t know where to find it right away. So, it uses DNS to look up the address (the IP address) of that website, along with its actual IP address, which the computer can understand. This way, you don’t have to remember complicated numbers—just the website name, and DNS takes care of the rest.

VOIP (Voice over Internet Protocol)

VOIP (Voice over Internet Protocol) is like making a phone call, but instead of using traditional phone lines, you're using the internet. Think of it like sending a letter through the postman, but instead of paper, you're sending a message electronically.

Imagine you're talking to a friend on the phone. Normally, your voice travels through wires and phone networks. With VOIP, your voice gets "converted" into digital data, like breaking down your voice into small packets, and then these packets travel over the internet, like how data is sent when browsing websites or sending messages.

AWS (Amazon Web Services)

AWS (Amazon Web Services) is like renting an office space in a big building instead of building your own office. Imagine you need a place to run your business, but instead of going through the trouble of buying land, constructing a building, and setting up everything from scratch, you decide to rent an office space in a big commercial building.

With AWS, instead of setting up your own servers, you rent them from Amazon. This means you don’t have to worry about the complex work of setting up and maintaining servers, as Amazon takes care of all that for you. Plus, just like an office building has many facilities like electricity, Wi-Fi, and meeting rooms, AWS gives you access to a lot of powerful tools for cloud computing—like storage, databases, and security—so you can focus on your work and not the infrastructure.

In short, AWS makes it easy for you to rent what you need in the cloud, just like renting an office, without the hassle of setting everything up yourself.

In this blog, we’ve simplified some of the most common and important terms used in networking and web communication. From understanding protocols and the request-response model to the roles of HTTP headers, cookies, and DNS, these concepts may seem intimidating at first, but with clear and simple explanations, they become much easier to grasp. By now, you should feel more confident in navigating the world of web technologies and explaining these terms to others. Remember, the more you familiarize yourself with these terms, the more comfortable you’ll become with the technology powering the internet!