Resource-based route organization in Express - Step-by-Step Execution

Concept Flow - Resource-based route organization

Define resource name

↓

Create router object

↓

Add routes for CRUD operations

↓

GET /resource

↓

Export router

↓

Use router in main app

This flow shows how to organize routes by resource, defining all CRUD routes in one router and then using it in the main app.

Execution Sample

Express

const express = require('express');
const router = express.Router();

router.get('/', (req, res) => res.send('List books'));
router.post('/', (req, res) => res.send('Create book'));

module.exports = router;

Defines GET and POST routes for the 'books' resource in a router, then exports it.

Execution Table

Step	Action	Route Registered	Handler Behavior	Effect
1	Create router object	No route yet	No handler yet	Router ready to add routes
2	Add GET / route	GET /	Responds with 'List books'	GET / route available
3	Add POST / route	POST /	Responds with 'Create book'	POST / route available
4	Export router	Routes ready	Handlers ready	Router can be imported
5	Use router in app	Routes active in app	Handlers respond to requests	App serves resource routes
6	Request GET /books	Matches GET /	Sends 'List books'	Client receives list
7	Request POST /books	Matches POST /	Sends 'Create book'	Client receives confirmation
8	Request GET /books/123	No route matches	404 Not Found	Client gets error

💡 Execution stops after all routes are registered and requests handled or not matched.

Variable Tracker

Variable	Start	After Step 2	After Step 3	After Step 4	After Step 5
router	undefined	Router with GET /	Router with GET and POST /	Router exported	Router used in app

Key Moments - 2 Insights

Why does GET /books/123 return 404 even though we have routes for /books?

Because the router only defines routes for / (which is mounted at /books) and does not define a route with an id parameter like /:id. The route for /books/:id is missing, so the request does not match any route (see execution_table step 8).

Why do we create a router instead of adding routes directly to the app?

Creating a router groups all resource routes together, making code organized and reusable. Then we attach the router to the app once (see concept_flow steps 2-5).

Visual Quiz - 3 Questions

Look at the execution_table, what is the router state after step 3?

A Router has GET / route only

B Router is exported

C Router has GET and POST / routes

D Router is used in the app

💡 Hint

Check the 'Route Registered' column at step 3 in execution_table

At which step does the app start responding to requests?

A Step 4

B Step 5

C Step 6

D Step 7

💡 Hint

Look for when the router is used in the app in execution_table

If we add router.get('/:id', ...), what changes in the execution_table?

A Step 8 request GET /books/123 will match and respond

B Step 6 request GET /books will fail

C POST /books route will be removed

D Router will no longer export

💡 Hint

Consider how adding a route affects request matching in execution_table step 8

Concept Snapshot

Resource-based route organization in Express:
- Create a router with express.Router()
- Define CRUD routes for a resource (GET, POST, PUT, DELETE) on the router's root path
- Export the router
- Use router in main app with app.use('/resource', router)
- Keeps routes organized and reusable

Full Transcript

This visual execution trace shows how to organize routes in Express by resource. First, a router object is created. Then routes for the resource are added, such as GET / and POST / on the router. The router is exported and used in the main app mounted at /books. Requests to these routes match the handlers and respond accordingly. Requests to undefined routes like GET /books/123 return 404. This method groups related routes, making code cleaner and easier to maintain.