By the end of this phase, you should be able to:
- Build a complete backend system
- Handle auth, caching, async work
- Write code like someone who understands backend — not just uses it
Reference aligned from your roadmap — but adapted for you.
- Runtime → Node.js
- Framework → Express.js
- DB → PostgreSQL
- Cache → Redis
- No switching frameworks
- No MongoDB distraction
- Build everything yourself once
- Understand WHY, not just HOW
Stop writing messy APIs. Start writing structured backend
- Express routing
- Middleware (core concept)
- Request validation
- Error handling (centralized)
Create API:
/users
GET
POST
DELETE
Add structure:
src/
├── routes/
├── controllers/
├── services/
├── middleware/
- ✔ You understand request flow
- ✔ You don't mix logic everywhere
Write DB logic that doesn't break
- Normalization basics
- Index (when to use)
- Avoid N+1 queries
- Transactions (basic idea)
- What caching is
- TTL
- When NOT to cache
- Add caching to your API
- Example:
- Cache user list
- Invalidate on update
- ✔ You reduce DB load
- ✔ You understand performance basics
Build auth properly (not copy-paste)
- Password hashing (bcrypt)
- JWT (access + refresh tokens)
- Sessions (basic understanding)
- Security basics
- Signup
- Login
- Protected routes
- ❌ Storing plain passwords
- ❌ Copying JWT code blindly
- ✔ You can build real login systems
Handle work outside request-response cycle
- Event loop (must understand)
- Async flow in Node
- Queues (basic)
Example:
- Email sender (fake or real)
- Background job (not blocking API)
Tools (simple start):
- Redis queue OR basic job simulation
- ✔ You understand scalable backend flow
Build ONE solid project combining everything:
Features:
- Auth (login/signup)
- PostgreSQL DB
- Redis caching
- Background job (email/logging)
- Clean API structure
phase-2/
├── full-backend-system/
├── README.md
- Architecture (very important)
- API endpoints
- How caching works
- How auth works
- What problems you faced
- 2–3 hrs → Backend
- 2 hrs → DSA
- 1 hr → Aptitude