1. You Fill the Form & Hit Submit

Example:

• Name

• Email

• Password

Your browser now sends this data to the backend using a POST request.

Something like:

{
  "name": "Shrashti",
  "email": "shrashti@example.com",
  "password": "mypassword123"
}

2. Backend Validates the Input

The backend checks:

• Is the email valid?

• Is the password long enough?

• Did the user enter all required fields?

• Does this email already exist?

If something is wrong → backend sends an error back.

3. Password Is Never Stored Directly

This is the MOST important step.

Your password is converted into a hashed version using algorithms like bcrypt.

For example:

"mypassword123" → "$2b$10$7hGd..."

This hash is what gets stored in the database.
Not the real password.

Even the developer cannot see the real password later.

4. User Is Saved in the Database

The backend creates a new user entry like:

{
  "id": "12345",
  "name": "Shrashti",
  "email": "shrashti@example.com",
  "passwordHash": "$2b$10$7hGd...",
  "createdAt": "2025-01-01"
}

That’s your account creation moment 🎉

5. The Server Creates a Token (Optional but Common)

Many apps log you in automatically after sign-up.

So the server generates a JWT token, which basically says:

“This person is now logged in.”

That token is sent back to your browser.

6. Browser Stores the Token

Your browser saves the token (usually in cookies or localStorage).
Now every request you make will include this token so the server knows it's you.

This is how you stay logged in.

⭐ In Short

When you hit Sign Up:

1. Form data → sent to backend

2. Backend validates it

3. Password is hashed

4. User record is stored

5. Token is generated

6. Browser stores login info

All of this happens in less than 0.2 seconds.

⭐ Final Note

This entire flow is the backbone of user registration in almost every website and app.
Understanding it helps you understand both backend and authentication more clearly — especially if you’re learning Node.js, Django, or any backend framework.

🪴 Introduction

We all use the “Login” button every day — on Instagram, Spotify, Netflix — but have you ever thought about what happens behind it?

As a backend developer and intern, I’ve learned that the “Login” process is like a short story where your browser, server, and database all talk to each other to confirm:

“Hey, is this really you?”

In this post, let’s break it down step-by-step in a simple way 🌱

⚙️ Step 1: You Click ‘Login’

When you enter your username and password and click Login, your frontend (website or app) collects that information and prepares to send it to the backend server — usually via an API request like this:

POST /login { "email": "shrashti@example.com", "password": "mypassword123" }

🧩 Step 2: Backend Receives the Request

The backend (often a Node.js + Express app) receives this data, validates it, and checks:

• Are all fields present?

• Is the data format correct?

If anything’s wrong (say, missing password), it sends back an error right away.

🗄️ Step 3: Database Check

Once the data looks fine, the backend connects to the database (like MongoDB) and searches for a matching email or username.

If the user exists, it fetches the stored (hashed) password.

🔐 Step 4: Password Verification

The backend never stores your real password — instead, it stores a hashed version (using libraries like bcrypt).
When you log in, it compares the hash of the password you entered with the stored one.

If they match → ✅ you’re verified.
If not → ❌ “Invalid Credentials.

🎟️ Step 5: Generating a Token (Session)

Once verified, the backend creates a JWT token (JSON Web Token) or session ID.
This token proves that you’re logged in, so you don’t need to re-enter your password every time.

Your browser stores it securely (in cookies or local storage).

🔁 Step 6: Accessing Your Account

Now, when you visit your profile or dashboard, the frontend sends that token to the backend with every request — and the backend checks:

“Is this a valid, unexpired token?”

If yes, it serves your personalized data (profile, messages, etc.).

And that’s how you get instant access 🎯

🌿 Conclusion

So next time you hit “Login,” remember — it’s not magic ✨
It’s a smart conversation between your frontend, backend, and database to make sure your data stays yours.

Learning how this flow works is one of the most fun parts of backend development — and this tiny process is the foundation for almost every secure app you use.

In the world of backend development, API stands for Application Programming Interface — but let’s simplify that.

🍕 Pizza Analogy:

🍕 How an API Works – Pizza Edition

1. User

🧍🏽‍♀️ You (the customer)
You say:

"I want a Margherita!"
✅ This represents the client (frontend) — making a request for data.

2. API (Waiter)

🤵 The waiter receives your request
He passes it to the kitchen without changing anything — just delivering the message.
✅ The API acts as a messenger between the client and server.

3. Kitchen (Backend/Server)

👨‍🍳 The chef prepares the pizza (data)
Backend processes your request, performs logic, accesses the database, etc.
✅ This is the server/backend, which prepares the "response".

4. API (Waiter)

🍕 Waiter picks up the pizza and brings it to you
✅ API delivers the result (data) back to the frontend.

5. User receives the Pizza (Response)

😋 You get the pizza you asked for!
✅ You receive the response — e.g., a JSON object.

That’s how API works!

🧠 Real Tech Version:

When you make a request like something searching on Google or any browser, your browser sends an request to a server, which processes the request and send back the response — usually in the form of data(JSON).

An API defines:

• How to request data

• What format to expect

• What happens if request fails

✅ Quick Example:

GET /order?item=margherita

Backend responds;

{
  "status": "success",
  "order": "1 Margherita Pizza"
}

🧩 My Take as a Backend Intern:

Learning APIs felt scary at first. But using analogies and small projects helped me get comfortable. Now I build and use daily.

🙌 Follow My Journey:

This is my first post as part of my backend dev journey at Shrashti from Backend Brains .
I’ll be posting weekly learnings, struggles, code examples, and beginner guides here.
Let’s grow together 🚀

🍕 APIs are like ordering pizza!

You're the customer.
API is your waiter.
Backend is the kitchen.
JSON is the pizza!

🍴 Simple, right? Follow Shrashti from Backend Brains for more backend dev analogies, tips, and guides!

#API #backend #webdevelopment #backendbrains