Request Lifecycle

This lesson covers Request Lifecycle. You do not need to memorize everything. Understand the flow first.

What you will learn

• What request lifecycle means — in normal words, not textbook words
• How it works step by step
• Code you can run today on your laptop
• Where teams use this in real projects

Before you start

• Software: Node.js LTS from nodejs.org, VS Code, and a terminal
• Knowledge: Earlier lessons in this Node.js course
• Previous lesson: Middleware — Complete Guide

Explain it simply

A request enters Express, passes through middleware, hits a route handler, and sends a response. Errors can go to error middleware.

Why developers use this

• Core skill for web backends
• Huge community and docs
• Leads to REST and auth

How it works (step by step)

1. A browser or app sends an HTTP request to your server.
2. Express middleware runs in order (log, parse JSON, check auth).
3. The route handler for Request Lifecycle runs your logic.
4. You send JSON or HTML back with the right status code (200, 201, 404, 500).

Code example — type this yourself

app.use(express.json());
app.get('/api/item', handler);
app.use((err, req, res, next) => {
  res.status(500).json({ error: err.message });
});

Order matters: body parser before routes, error handler last.

What each part does

• app.use(express.json()); — Line 1: runs as written.
• app.get('/api/item', handler); — Defines what happens when a client hits this URL and HTTP method.
• app.use((err, req, res, next) => { — Line 3: runs as written.
• res.status(500).json({ error: err.message }); — Line 4: runs as written.
• }); — Line 5: runs as written.

Real life: where Request Lifecycle shows up

A college admin panel uses Request Lifecycle with Express: students hit /courses, teachers hit /grades, and shared middleware checks login once for every page.

Try it yourself — hands-on

1. Create a new file (e.g. request-lifecycle-demo.js) in an empty folder
2. Type the example code for Request Lifecycle yourself — typing helps memory
3. Run node on that file and read the output
4. Change one line (a value, a message, a route path) and run again to see what breaks or improves

Common mistakes (avoid these)

• Skipping the terminal — Request Lifecycle only feels easy after you run code yourself.

Interview note

Be ready to explain Request Lifecycle with a real trade-off: what problem it solves and what you would not use it for.

Summary

• You can explain Request Lifecycle in your own words
• You ran working code — not just read about it
• You know one mistake to avoid and one real place teams use this