Controller pattern for route handlers in Express - Performance & Optimization

Performance: Controller pattern for route handlers

MEDIUM IMPACT

This pattern affects server response time and how quickly the server can handle incoming requests, indirectly influencing perceived page load speed.

Handling HTTP requests in an Express app

Express

const userController = {
  listActiveUsers: (req, res) => {
    const users = database.getUsers();
    const filtered = users.filter(u => u.active);
    res.json(filtered);
  }
};
app.get('/users', userController.listActiveUsers);

Separates concerns by moving logic to controller functions, enabling reuse, easier testing, and potentially caching or optimization.

📈 Performance GainReduces duplicated CPU work and improves maintainability, leading to faster response times under load

Handling HTTP requests in an Express app

Express

app.get('/users', (req, res) => {
  // complex logic directly in route
  const users = database.getUsers();
  const filtered = users.filter(u => u.active);
  res.json(filtered);
});

All logic is inside the route handler, making it harder to maintain and potentially causing duplicated code and slower response times due to lack of reuse.

📉 Performance CostIncreases server CPU usage and response time under load due to repeated inline logic

Performance Comparison

Pattern	Server CPU Usage	Code Maintainability	Response Time	Verdict
Inline route logic	High due to repeated code	Low, hard to maintain	Slower under load	[X] Bad
Controller pattern	Lower with reuse and caching	High, easier to maintain	Faster and scalable	[OK] Good

Rendering Pipeline

The controller pattern organizes server-side logic before sending responses, affecting how quickly the server can prepare data for the client. This impacts the time until the browser receives content to render.

→Server Processing

→Network Transfer

→Browser Rendering

⚠️ BottleneckServer Processing due to complex inline logic in routes

Core Web Vital Affected

LCP

This pattern affects server response time and how quickly the server can handle incoming requests, indirectly influencing perceived page load speed.

Optimization Tips

1Keep route handlers simple by moving logic to controllers.

2Reuse controller functions to avoid duplicated CPU work.

3Optimize controller code to reduce server response time and improve LCP.

Performance Quiz - 3 Questions

How does using the controller pattern for route handlers affect server response time?

A It has no effect on response time

B It can reduce response time by organizing and reusing logic

C It always increases response time due to extra function calls

D It blocks the browser rendering process

DevTools: Network and Performance panels

How to check: Use Network panel to measure server response time for routes; use Performance panel to profile server-side code if possible or use external profiling tools.

What to look for: Look for long server response times and CPU spikes indicating inefficient route handling

Practice

1. What is the main purpose of using the controller pattern in Express route handlers?

easy

A. To separate route logic from routing setup for better organization

B. To combine all route handlers into a single file

C. To directly write SQL queries inside route handlers

D. To avoid using middleware functions in routes

Solution

1. Step 1: Understand the controller pattern concept

   The controller pattern means moving the logic that handles requests out of the route definitions into separate functions or files.

2. Step 2: Identify the benefit of separation

   This separation improves code organization, making it easier to read and maintain.

3. Final Answer:

   To separate route logic from routing setup for better organization -> Option A

4. Quick Check:

   Controller pattern = separation of concerns [OK]

Hint: Controllers keep route files clean and logic separate [OK]

Common Mistakes:

• Thinking controllers combine all routes in one file
• Believing controllers write database queries directly
• Confusing controllers with middleware avoidance

2. Which of the following is the correct way to import and use a controller function named getUser in an Express route?

easy

A. router.get('/user', getUser());

B. router.get('/user', () => getUser);

C. router.get('/user', getUser => {});

D. router.get('/user', getUser);

Solution

1. Step 1: Understand how to pass controller functions

   In Express, route handlers expect a function reference, not the result of calling the function.

2. Step 2: Identify correct syntax

   Passing getUser without parentheses passes the function itself. Using parentheses calls it immediately, which is incorrect here.

3. Final Answer:

   router.get('/user', getUser); -> Option D

4. Quick Check:

   Pass function reference without () [OK]

Hint: Pass controller as function reference, no parentheses [OK]

Common Mistakes:

• Calling the controller function immediately with ()
• Using arrow functions incorrectly wrapping the controller
• Returning the function instead of calling it

3. Given this controller function and route setup, what will be the response when a GET request is made to /hello?

const sayHello = (req, res) => {
  res.send('Hello from controller!');
};

router.get('/hello', sayHello);

medium

A. Hello from controller!

B. Error: sayHello is not a function

C. No response, request hangs

D. 404 Not Found

Solution

1. Step 1: Analyze the controller function behavior

   The sayHello function sends a plain text response 'Hello from controller!' when called.

2. Step 2: Check route setup correctness

   The route uses sayHello correctly as the handler for GET requests to '/hello'.

3. Final Answer:

   Hello from controller! -> Option A

4. Quick Check:

   Controller sends response text [OK]

Hint: Controller sends response, route calls it correctly [OK]

Common Mistakes:

• Forgetting to call res.send inside controller
• Passing controller incorrectly causing runtime error
• Misreading route path causing 404

4. Identify the error in this Express controller pattern usage:

const userController = {
  getUser: (req, res) => {
    res.json({ name: 'Alice' });
  }
};

router.get('/user', userController.getUser());

medium

A. res.json should be res.send

B. Missing import statement for router

C. Calling userController.getUser() immediately instead of passing function

D. Route path should be '/users' not '/user'

Solution

1. Step 1: Check how controller function is passed

   The code calls userController.getUser() immediately, which runs the function and passes its result, not the function itself.

2. Step 2: Understand correct usage

   Express expects a function reference as the route handler, so it should be userController.getUser without parentheses.

3. Final Answer:

   Calling userController.getUser() immediately instead of passing function -> Option C

4. Quick Check:

   Pass function reference, not call it [OK]

Hint: Don't add () when passing controller to route [OK]

Common Mistakes:

• Calling controller function instead of passing it
• Confusing res.json and res.send (both valid here)
• Assuming route path naming causes error

5. You want to organize your Express app using the controller pattern. You have multiple routes for users: getUser, createUser, and deleteUser. Which approach best follows the controller pattern for clean code?

hard

A. Put all route definitions and logic inside a single routes.js file without controllers

B. Define all user-related functions in a separate userController.js file and import them in the router file

C. Write all user route handlers directly inside the main app.js file

D. Use inline anonymous functions for each route in the router file

Solution

1. Step 1: Understand controller pattern best practice

   Controllers group related route logic into separate files or modules to keep code organized and reusable.

2. Step 2: Evaluate options for clean code

   Defining all user-related functions in a dedicated userController.js file and importing them into the router file follows the pattern well.

3. Final Answer:

   Define all user-related functions in a separate userController.js file and import them in the router file -> Option B

4. Quick Check:

   Separate logic into controller files [OK]

Hint: Group related handlers in controller files, import in routes [OK]

Common Mistakes:

• Putting all logic in main app file making it messy
• Mixing routes and logic in one file without separation
• Using anonymous functions inline reduces reusability