Dynamic Rendering

This lesson covers Dynamic Rendering. Here is the idea in simple words, then we write real code.

What you will learn

• What dynamic rendering 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: EJS Layouts — Complete Guide

Explain it simply

Dynamic rendering means the HTML changes per user — show their name, role, or data from the database.

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 Dynamic Rendering 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.get('/profile', async (req, res) => {
  const profile = await db.getProfile(req.user.id);
  res.render('profile', { profile });
});

Fetch data before res.render. Keep templates dumb — logic stays in the route or service.

What each part does

• app.get('/profile', async (req, res) => { — Defines what happens when a client hits this URL and HTTP method.
• const profile = await db.getProfile(req.user.id); — Async work — Node can serve other users while this waits.
• res.render('profile', { profile }); — Line 3: runs as written.
• }); — Line 4: runs as written.

Real life: where Dynamic Rendering shows up

A college admin panel uses Dynamic Rendering 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. dynamic-rendering-demo.js) in an empty folder
2. Type the example code for Dynamic Rendering 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 — Dynamic Rendering only feels easy after you run code yourself.

Interview note

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

Summary

• You can explain Dynamic Rendering 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