Namespaces for separation in Express - Step-by-Step Execution

Concept Flow - Namespaces for separation

Start Express App

↓

Define Namespace 1

↓

Add Routes to Namespace 1

↓

Define Namespace 2

↓

Add Routes to Namespace 2

↓

Mount Namespaces on App

↓

App Listens for Requests

↓

Request Matches Namespace Route

↓

Namespace Route Handler Executes

↓

Response Sent

↓

End

This flow shows how an Express app defines separate namespaces (route groups) to organize routes, mounts them, and handles requests within each namespace.

Execution Sample

Express

const express = require('express');
const app = express();

const apiV1 = express.Router();
apiV1.get('/users', (req, res) => res.send('Users v1'));

const apiV2 = express.Router();
apiV2.get('/users', (req, res) => res.send('Users v2'));

app.use('/api/v1', apiV1);
app.use('/api/v2', apiV2);

app.listen(3000);

This code creates two namespaces (/api/v1 and /api/v2) with separate /users routes, then starts the server.

Execution Table

Step	Action	Namespace	Route	Request URL	Handler Response
1	Create Express app	-	-	-	-
2	Create Router apiV1	apiV1	-	-	-
3	Add GET /users to apiV1	apiV1	/users	-	-
4	Create Router apiV2	apiV2	-	-	-
5	Add GET /users to apiV2	apiV2	/users	-	-
6	Mount apiV1 at /api/v1	apiV1	-	-	-
7	Mount apiV2 at /api/v2	apiV2	-	-	-
8	Request GET /api/v1/users	apiV1	/users	/api/v1/users	Users v1
9	Request GET /api/v2/users	apiV2	/users	/api/v2/users	Users v2
10	Request GET /api/v3/users (no match)	-	-	/api/v3/users	404 Not Found

💡 Requests outside defined namespaces return 404; app listens indefinitely.

Variable Tracker

Variable	Start	After Step 2	After Step 4	After Step 6	After Step 7	Final
app	Express app instance	Express app instance	Express app instance	Express app with apiV1 mounted	Express app with apiV1 and apiV2 mounted	Running server
apiV1	undefined	Router instance	Router instance	Router instance	Router instance	Router with /users route
apiV2	undefined	undefined	Router instance	Router instance	Router instance	Router with /users route

Key Moments - 3 Insights

Why do requests to /api/v1/users and /api/v2/users return different responses?

Because each namespace (apiV1 and apiV2) has its own router with a separate /users route handler, as shown in execution_table rows 8 and 9.

What happens if a request is made to a URL not matching any namespace?

The app returns a 404 Not Found response since no route matches, as shown in execution_table row 10.

Why do we use express.Router() to create namespaces?

express.Router() creates isolated route groups (namespaces) so routes can be organized and mounted separately, as seen in steps 2, 4, 6, and 7.

Visual Quiz - 3 Questions

Look at the execution_table row 8. What response does the GET request to /api/v1/users return?

A 404 Not Found

B Users v1

C Users v2

D Error

💡 Hint

Check the Handler Response column in row 8 for the /api/v1/users request.

At which step is the apiV2 router mounted on the app?

A Step 4

B Step 6

C Step 7

D Step 9

💡 Hint

Look at the Action column for mounting routers in the execution_table.

If we add a new route /products to apiV1, how would the variable_tracker for apiV1 change after Step 7?

A apiV1 router now has /users and /products routes

B No change, still only /users route

C apiV1 router replaced by apiV2 router

D apiV1 router removed

💡 Hint

Variable tracker shows routes inside routers; adding a route updates the router's routes.

Concept Snapshot

Namespaces in Express use express.Router() to group routes.
Each namespace handles its own routes separately.
Mount namespaces on the main app with app.use(path, router).
Requests match namespace path + route path.
This keeps routes organized and separated.
Unmatched requests return 404.

Full Transcript

This visual execution shows how Express uses namespaces to separate routes. We start by creating an Express app. Then we create two routers, apiV1 and apiV2, each with their own /users route. We mount apiV1 at /api/v1 and apiV2 at /api/v2 on the main app. When a request comes in, Express matches the URL to the mounted namespace and then to the route inside that namespace. For example, GET /api/v1/users triggers the apiV1 router's /users handler, returning 'Users v1'. Similarly, GET /api/v2/users triggers apiV2's handler, returning 'Users v2'. Requests to unknown paths like /api/v3/users get a 404 Not Found response. This separation helps organize routes clearly and avoid conflicts. The variable tracker shows how routers and app state change as we add and mount namespaces. Key moments clarify why different namespaces respond differently and why unmatched routes return 404. The quiz tests understanding of these steps and state changes.