Why Does Backend Exist?

The Request Flow

Click each step to understand its role in the journey.

Why frontend alone isn't enough

The Mental Model

Click to expand the layers of a modern architecture.

Let's build the smallest possible backend.

No frameworks. No Express. Just pure Node.js.

const http = require('http');

const server = http.createServer((req, res) => {
  if (req.url === '/api/user') {
    res.writeHead(200, { 'Content-Type': 'application/json' });
    res.end(JSON.stringify({ name: 'Hamza', role: 'Engineer' }));
  } else {
    res.writeHead(404);
    res.end('Not Found');
  }
});

server.listen(3000, () => {
  console.log('Backend listening on port 3000');
});

Common Misconceptions

• ❌ Backend means Node.js
  Node.js is just a runtime environment. Backend is a concept. You can write a backend in Python, Go, Java, or Rust.
• ❌ Backend means Express
  Express is just a framework that makes writing Node.js backends easier. As we saw above, pure Node.js is the actual backend.
• ❌ Backend means Database
  The database is just a storage tool. The backend is the logical server that stands between the frontend and the database to enforce rules.

Common Mistakes

• ❌ Storing API keys or secrets on the frontend.
  Anything on the frontend can be viewed by anyone who opens DevTools. Secrets must only live on the backend.
• ❌ Trusting data because the frontend validated it.
  Frontend validation is for UX (User Experience). Backend validation is for Security. Malicious actors can easily bypass frontend validation using tools like Postman or cURL.

Performance Considerations