When I started learning backend development, I kept hearing terms like protocols, databases, HTTP, and pub-sub. At first, they sounded complicated — but once I broke them down, everything started to make sense.

In this blog, I’ll explain these backend fundamentals in a simple and practical way.

This is my first blog where I break down backend concepts I recently learned in a simple way. I’ve been learning these concepts by following the Harkirat Singh youtube channel, especially his full stack roadmap video . His explanations helped me understand how backend systems actually work behind the scenes.

---

🌐 1. Communication Protocols (How Computers Talk)

For two computers to communicate, they must be connected through a network. But connection alone isn’t enough — they also need rules to understand each other.

These rules are called protocols.

---

📦 Types of Protocols

🔹 Transport Layer Protocols

These control how data is sent between systems.

✅ TCP (Transmission Control Protocol)

• Reliable and ordered communication

• Ensures all data reaches correctly

Example: When you open a website, TCP ensures all files (HTML, CSS, JS) are received properly.

⚡ UDP (User Datagram Protocol)

• Faster but less reliable

• No guarantee of delivery

Example: Used in video streaming or online gaming where speed matters more than accuracy.

---

🔹 Application Layer Protocol

🌍 HTTP (HyperText Transfer Protocol)

• Used by browsers to communicate with servers

• Works on top of TCP

Example Flow:

1. You type google.com

2. Browser sends an HTTP request

3. Server responds with data (HTML page)

4. Browser renders it

---

🗄️ 2. Databases (Where Data Lives)

Backend applications deal with a lot of data — users, passwords, posts, etc.

Storing all this directly in backend code is inefficient and slow.

👉 So we use databases — a separate system designed to store and manage data efficiently.

---

📊 Types of Databases

🔹 SQL Databases (Structured)

• MySQL

• PostgreSQL

Data stored in tables (rows & columns)

Example:

id	name	email
1	Saga	saga@mail.com

---

🔹 NoSQL Databases (Flexible)

• MongoDB

• Firebase

Data stored as JSON-like objects

Example:

{
  "name": "Saga",
  "email": "saga@mail.com"
}

---

🔄 How Browser Interacts with Database

Browser never talks directly to the database.

Instead:

Browser → HTTP Request → Backend → Database
                             ↓
                    Fetch / Store Data
                             ↓
Browser ← HTTP Response ← Backend

---

⚡ Why Databases Are Needed

• Backend alone becomes slow with large data

• Databases are optimized for:

  • Fast queries

  • Efficient storage

  • Data security

---

📡 3. Messaging Systems (Pub/Sub)

As applications grow, direct communication between services becomes messy.

👉 That’s where Pub/Sub (Publish–Subscribe) comes in.

---

🧠 Concept

• Publisher → sends message

• Subscriber → receives message

• Message Broker → handles communication

---

📦 Example

Imagine an e-commerce app:

1. User places an order

2. Order service publishes: "Order Created"

Now multiple services can react:

• Payment service → processes payment

• Email service → sends confirmation

• Delivery service → starts shipping

👉 All this happens without direct connection between services

---

⚡ Why Pub/Sub?

• Loose coupling (services don’t depend on each other)

• Scalable systems

• Better performance

---

🏗️ 4. HTTP Server Architecture

Now let’s connect everything together.

---

🌐 Request Flow

Browser → HTTP Server

The browser sends:

🔹 URL / Route

Example:

/users
/login

---

🔹 HTTP Methods

• GET → Fetch data

• POST → Send data

• PUT → Update data

• DELETE → Remove data

---

🔹 Headers

Extra information about request

Example:

Content-Type: application/json
Authorization: Bearer token

---

🔹 Query Parameters

Used to send small data in URL

Example:

/users?page=2&limit=10

---

📄 Pagination (Important Concept)

When there is a large amount of data, we don’t send everything at once.

👉 Instead, we send it in parts.

Example:

/products?page=1&limit=10

• page=1 → first set of data

• limit=10 → number of items per request

---

🔹 Request Body

Used in POST/PUT requests

Example:

{
  "email": "test@gmail.com",
  "password": "123"
}

---

🔹 Cookies

Used to store small data like:

• Login sessions

• User preferences

---

📤 Server Response

After processing, server sends response back.

---

🔹 Status Codes

• 200 → Success

• 201 → Created

• 403 → Forbidden

• 404 → Not Found

---

🔹 Response Types

📄 Text

Hello World

📦 JSON

{
  "message": "Success"
}

🌐 HTML

Used to render web pages

---

🔹 Response Headers

Provide metadata about response

Example:

Content-Type: application/json

---

🔁 Full Cycle Summary

Browser → HTTP Request → Server → Database
                                 ↓
                         Process Data
                                 ↓
Browser ← HTTP Response ← Server

---

🚀 Final Thoughts

Understanding backend jargon is the first step toward becoming a solid developer.

• Protocols → define communication rules

• Databases → manage data efficiently

• Pub/Sub → handles large-scale communication

• HTTP → connects everything together

Once you understand these concepts, backend development becomes much easier and more logical.

---

🔜 What’s Next?

Now that I understand the theory, I started implementing it by building an HTTP server from scratch in Node.js.

That’s where things started getting really interesting.

---

Thanks for reading 🙌