Service layer pattern in Express

Introduction

The service layer pattern helps organize your code by separating business logic from request handling. It makes your app easier to read and maintain.

When you want to keep your route handlers simple and clean.

When your app has complex business rules that need clear organization.

When you want to reuse logic across different parts of your app.

When you want to make testing your business logic easier.

When you want to separate concerns for better teamwork and scaling.

Syntax

Express

class ServiceName {
  async methodName(params) {
    // business logic here
  }
}

module.exports = new ServiceName();

The service class contains methods with your app's main logic.

Route handlers call these service methods to keep routes simple.

Examples

A simple service to get user data by ID.

Express

class UserService {
  async getUserById(id) {
    // fetch user from database
  }
}

module.exports = new UserService();

Service handling order creation logic.

Express

class OrderService {
  async createOrder(orderData) {
    // validate and save order
  }
}

module.exports = new OrderService();

Sample Program

This example shows a simple Express app using a service layer. The UserService holds user data and logic to find a user by ID. The route handler calls the service method to get the user and sends the response. This keeps the route clean and focused on HTTP details.

Express

const express = require('express');
const app = express();
app.use(express.json());

// Service layer
class UserService {
  constructor() {
    this.users = [{ id: 1, name: 'Alice' }, { id: 2, name: 'Bob' }];
  }

  async getUserById(id) {
    return this.users.find(user => user.id === id) || null;
  }
}

const userService = new UserService();

// Route handler
app.get('/users/:id', async (req, res) => {
  const id = Number(req.params.id);
  const user = await userService.getUserById(id);
  if (user) {
    res.json(user);
  } else {
    res.status(404).json({ message: 'User not found' });
  }
});

app.listen(3000, () => console.log('Server running on http://localhost:3000'));

Important Notes

Keep service methods focused on business logic only.

Services can be reused in different routes or parts of your app.

Testing services separately is easier than testing routes with logic mixed in.

Summary

The service layer pattern separates business logic from route handling.

It helps keep your code organized, clean, and easier to maintain.

Use services to reuse logic and simplify testing.

Practice

1. What is the main purpose of the service layer pattern in an Express application?

easy

A. To manage database connections only

B. To handle HTTP requests and responses directly

C. To separate business logic from route handling for cleaner code

D. To serve static files like images and CSS

Solution

1. Step 1: Understand the role of route handlers

   Route handlers in Express mainly handle HTTP requests and responses, not business logic.

2. Step 2: Identify the service layer role

   The service layer contains business logic, keeping route handlers clean and focused on HTTP concerns.

3. Final Answer:

   To separate business logic from route handling for cleaner code -> Option C

4. Quick Check:

   Service layer = separates logic [OK]

Hint: Service layer keeps logic out of routes for clarity [OK]

Common Mistakes:

• Confusing service layer with route handlers
• Thinking service layer manages HTTP directly
• Assuming service layer only handles database connections

2. Which of the following is the correct way to use a service function inside an Express route handler?

easy

A. const result = serviceFunction(); res.send(result);

B. res.send(serviceFunction);

C. serviceFunction(res);

D. res.send(await serviceFunction);

Solution

1. Step 1: Understand service function usage

   Service functions are called to get results, which are then sent in the response.

2. Step 2: Check syntax correctness

   const result = serviceFunction(); res.send(result); calls the function and sends its result correctly. res.send(serviceFunction); sends the function itself, not its result. serviceFunction(res); wrongly passes response object to service. res.send(await serviceFunction); misses parentheses and awaits incorrectly.

3. Final Answer:

   const result = serviceFunction(); res.send(result); -> Option A

4. Quick Check:

   Call service, then send result [OK]

Hint: Call service function, then send its result [OK]

Common Mistakes:

• Sending the function instead of its result
• Passing Express response object to service
• Incorrect use of async/await syntax

3. Given this Express route and service code, what will be the response when a GET request is made to /user/42?

const userService = {
  getUserById: (id) => ({ id, name: `User${id}` })
};

app.get('/user/:id', (req, res) => {
  const user = userService.getUserById(req.params.id);
  res.json(user);
});

medium

A. {"id":"42","name":"User"}

B. {"id":42,"name":"User42"}

C. Error: getUserById is not a function

D. {"id":"42","name":"User42"}

Solution

1. Step 1: Analyze service function output

   The service returns an object with id as string and name as 'User' plus id string.

2. Step 2: Check route response

   The route sends JSON of the user object, so id remains a string "42" and name is "User42".

3. Final Answer:

   {"id":"42","name":"User42"} -> Option D

4. Quick Check:

   Service returns object with string id [OK]

Hint: Check data types returned by service [OK]

Common Mistakes:

• Assuming id is a number instead of string
• Expecting an error from correct code
• Ignoring string concatenation in name

4. Identify the error in this Express route using a service layer:

app.get('/items', (req, res) => {
  const items = itemService.getAllItems;
  res.json(items);
});

medium

A. Incorrect route path syntax

B. Missing parentheses when calling getAllItems function

C. res.json cannot send arrays

D. itemService is not defined

Solution

1. Step 1: Check function call syntax

   The code assigns the function itself to items without calling it (missing parentheses).

2. Step 2: Understand impact on response

   res.json(items) sends the function reference, not the data, causing wrong output or error.

3. Final Answer:

   Missing parentheses when calling getAllItems function -> Option B

4. Quick Check:

   Call functions with () to get results [OK]

Hint: Always use () to call service functions [OK]

Common Mistakes:

• Forgetting parentheses on function calls
• Thinking res.json can't send arrays
• Assuming route path syntax is wrong

5. You want to add error handling in your service layer for a function that fetches a user by ID asynchronously. Which approach correctly separates concerns and handles errors in Express using the service layer pattern?

// Service function
async function getUserById(id) {
  if (!id) throw new Error('ID required');
  // simulate async DB call
  return { id, name: `User${id}` };
}

// Route handler
app.get('/user/:id', async (req, res) => {
  try {
    const user = await getUserById(req.params.id);
    res.json(user);
  } catch (err) {
    res.status(400).json({ error: err.message });
  }
});

hard

A. Correctly separates logic and handles errors in route

B. Error handling should be inside the route only

C. Service should send response directly, not return data

D. Try/catch is unnecessary with async functions

Solution

1. Step 1: Check separation of concerns

   The service function only throws errors or returns data, no response handling.

2. Step 2: Verify error handling location

   The route handler catches errors and sends HTTP responses, keeping concerns separate.

3. Final Answer:

   Correctly separates logic and handles errors in route -> Option A

4. Quick Check:

   Service throws errors; route handles responses [OK]

Hint: Throw errors in service; catch and respond in route [OK]

Common Mistakes:

• Putting response logic inside service functions
• Ignoring try/catch for async errors
• Handling errors only in service without route awareness