Express application structure - Performance & Optimization

Performance: Express application structure

MEDIUM IMPACT

This affects the server response time and how quickly the server can handle requests, impacting the time to first byte (TTFB).

Organizing routes and middleware in an Express app

Express

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

const userRouter = express.Router();
userRouter.get('/', (req, res) => {
  res.send('User page');
});

const adminRouter = express.Router();
adminRouter.use((req, res, next) => {
  // heavy middleware only for admin routes
  for(let i=0; i<1000000; i++) {}
  next();
});
adminRouter.get('/', (req, res) => {
  res.send('Admin page');
});

app.use('/user', userRouter);
app.use('/admin', adminRouter);

app.listen(3000);

Heavy middleware runs only on admin routes, reducing unnecessary processing on other routes.

📈 Performance GainReduces average request processing time by avoiding middleware on unrelated routes.

Organizing routes and middleware in an Express app

Express

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

app.use((req, res, next) => {
  // heavy middleware runs on every request
  for(let i=0; i<1000000; i++) {}
  next();
});

app.get('/user', (req, res) => {
  res.send('User page');
});

app.get('/admin', (req, res) => {
  res.send('Admin page');
});

app.listen(3000);

Heavy middleware runs on every request, even when not needed, causing unnecessary delay.

📉 Performance CostBlocks response for all routes, increasing TTFB by 50-100ms depending on middleware complexity.

Performance Comparison

Pattern	Middleware Runs	Request Delay	Server Load	Verdict
Global heavy middleware	Runs on all requests	Increases TTFB by 50-100ms	Higher CPU usage	[X] Bad
Scoped middleware per router	Runs only on relevant routes	Minimal delay on unrelated routes	Lower CPU usage	[OK] Good

Rendering Pipeline

Express app structure affects how the server processes incoming requests through middleware and route handlers before sending a response.

→Middleware execution

→Route matching

→Response generation

⚠️ BottleneckMiddleware execution when applied globally without route scoping

Optimization Tips

1Avoid running heavy middleware globally; scope it to routes that need it.

2Organize routes using routers to isolate middleware and reduce processing.

3Keep middleware lightweight to minimize server response delays.

Performance Quiz - 3 Questions

What is a performance benefit of scoping middleware to specific routes in Express?

A Middleware runs faster on all routes

B Middleware runs only when needed, reducing unnecessary processing

C Middleware is cached by the browser

D Middleware reduces server memory usage

DevTools: Network panel in browser DevTools and server-side profiling tools

How to check: Use Network panel to measure TTFB for different routes; use Node.js profiler or logging to check middleware execution time

What to look for: Long TTFB or high CPU usage on routes without heavy middleware indicates inefficient structure

Practice

1. What is the main purpose of the app.js file in an Express application?

easy

A. To set up the Express server, middleware, and routes

B. To store database connection details only

C. To write frontend HTML code

D. To handle user authentication exclusively

Solution

1. Step 1: Understand the role of app.js

   The app.js file is the main entry point where the Express server is created and configured.

2. Step 2: Identify what app.js typically contains

   It usually sets up middleware, routes, and starts the server listening on a port.

3. Final Answer:

   To set up the Express server, middleware, and routes -> Option A

4. Quick Check:

   Main server setup = C [OK]

Hint: Remember: app.js is the main server setup file [OK]

Common Mistakes:

• Confusing app.js with frontend files
• Thinking app.js only handles database
• Assuming app.js is for authentication only

2. Which of the following is the correct way to import the Express module and create an app instance in app.js?

easy

A. import app from 'express'; const express = app();

B. import express from 'express'; const app = express();

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

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

Solution

1. Step 1: Recall common Express import syntax

   Express is commonly imported using CommonJS syntax: const express = require('express');

2. Step 2: Create app instance correctly

   The app instance is created by calling express(), so const app = express(); is correct.

3. Final Answer:

   const express = require('express'); const app = express(); -> Option D

4. Quick Check:

   CommonJS import + app creation = A [OK]

Hint: Use require() and call express() to create app [OK]

Common Mistakes:

• Mixing ES module import with CommonJS require
• Calling require('express') directly without variable
• Incorrect import syntax like importing app instead of express

3. Given this Express app structure snippet in app.js:

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

app.use('/api', require('./routes/api'));

app.listen(3000);

What happens when a user visits http://localhost:3000/api/users?

medium

A. The server returns a 404 error because no route is defined

B. The request is handled by the router defined in ./routes/api

C. The server crashes due to missing route handler

D. The request is handled by the root route /

Solution

1. Step 1: Understand app.use('/api', ...) behavior

   This mounts the router from ./routes/api at the path /api.

2. Step 2: Analyze the request URL /api/users

   The request matches the /api prefix, so it is forwarded to the router in ./routes/api which should handle /users.

3. Final Answer:

   The request is handled by the router defined in ./routes/api -> Option B

4. Quick Check:

   Mounted router handles prefixed routes = B [OK]

Hint: Routes under '/api' go to './routes/api' router [OK]

Common Mistakes:

• Assuming 404 because route not in app.js
• Thinking server crashes without explicit route in app.js
• Confusing root route with mounted router path

4. Consider this Express app snippet:

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

app.use((req, res) => {
  res.send('');
});

app.get('/home', (req, res) => {
  res.send('Welcome Home');
});

app.listen(3000);

Why does visiting http://localhost:3000/home return a blank page?

medium

A. Because the route handler is not properly defined or not reached

B. Because the server is not listening on port 3000

C. Because the middleware to parse requests is missing

D. Because res.send is missing a return statement

Solution

1. Step 1: Check if route handler is correct

   The route /home is defined with app.get and sends a response.

2. Step 2: Consider possible reasons for blank response

   If the page is blank, it usually means the route handler is not reached or overridden by other middleware or routes.

3. Final Answer:

   Because the route handler is not properly defined or not reached -> Option A

4. Quick Check:

   Blank page means route not reached = D [OK]

Hint: Blank page usually means route handler not reached [OK]

Common Mistakes:

• Thinking res.send needs return statement
• Assuming server not listening without error
• Confusing missing middleware with route handling

5. You want to organize your Express app by separating routes into different files. Which structure correctly shows how to use a separate users.js route file inside a routes folder and mount it in app.js?

hard

A. // In routes/users.js
const router = require('express.Router')();
router.get('/', (req, res) => res.send('Users list'));
module.exports = router;

// In app.js
app.use('/users', require('./routes/users'));

B. // In routes/users.js
module.exports = (req, res) => res.send('Users list');

// In app.js
app.use('/users', require('./routes/users'));

C. // In routes/users.js
const express = require('express');
const router = express.Router();
router.get('/', (req, res) => res.send('Users list'));
module.exports = router;

// In app.js
const usersRouter = require('./routes/users');
app.use('/users', usersRouter);

D. // In routes/users.js
const express = require('express');
const router = express.Router;
router.get('/', (req, res) => res.send('Users list'));
module.exports = router;

// In app.js
const usersRouter = require('./routes/users');
app.use('/users', usersRouter);

Solution

1. Step 1: Check correct router creation in users.js

   The router should be created with express.Router(), not express() or other calls.

2. Step 2: Verify correct export and mounting in app.js

   The router is exported with module.exports and mounted with app.use('/users', usersRouter);.

3. Final Answer:

   Using express.Router() in the route file and proper mounting -> Option C

4. Quick Check:

   Use express.Router() and app.use() = A [OK]

Hint: Use express.Router() in route files and mount with app.use() [OK]

Common Mistakes:

• Using express() instead of express.Router() for router
• Exporting a function instead of a router object
• Not mounting the router with app.use() properly