Service layer pattern in Express - Step-by-Step Execution

Concept Flow - Service layer pattern

Client Request

↓

Controller receives request

↓

Controller calls Service Layer

↓

Service Layer processes logic

↓

Service Layer calls Data Access Layer

↓

Data Access Layer interacts with DB

↓

Data returned to Service Layer

↓

Service Layer returns result to Controller

↓

Controller sends response to Client

The service layer acts as a middleman between controllers and data access, handling business logic and keeping code organized.

Execution Sample

Express

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

Controller receives a request, calls the service layer to get user data, then sends it back as JSON.

Execution Table

Step	Action	Input	Service Layer Call	Service Result	Controller Response
1	Receive GET /users/42	id=42	Call getUserById(42)	Pending	Pending
2	Service queries DB for user 42	id=42	DB query executed	{ id: 42, name: 'Alice' }	Pending
3	Service returns user data	user data	Return { id: 42, name: 'Alice' }	{ id: 42, name: 'Alice' }	Pending
4	Controller sends JSON response	user data	No call	No change	Response: { id: 42, name: 'Alice' }
5	Request complete	N/A	N/A	N/A	Response sent to client

💡 Request completes after controller sends user data response

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	After Step 4	Final
req.params.id	undefined	42	42	42	42	42
user	undefined	undefined	Pending	{ id: 42, name: 'Alice' }	{ id: 42, name: 'Alice' }	{ id: 42, name: 'Alice' }

Key Moments - 2 Insights

Why does the controller not access the database directly?

The controller calls the service layer (see execution_table step 1 and 3) to keep business logic separate and make code easier to maintain.

What happens if the service layer takes time to get data?

The controller waits asynchronously (step 1 shows 'Pending') until the service returns data before sending a response.

Visual Quiz - 3 Questions

Look at the execution_table at step 2, what is the service layer doing?

A Querying the database for user data

B Sending response to client

C Receiving client request

D Returning data to controller

💡 Hint

Check the 'Service Layer Call' and 'Service Result' columns at step 2

At which step does the controller send the response to the client?

A Step 1

B Step 3

C Step 4

D Step 5

💡 Hint

Look at the 'Controller Response' column for when the response is sent

If the service layer returned null instead of user data, what would change in the execution_table?

A Controller Response at step 4 would be unchanged

B Service Result at step 3 would be null

C Request would complete at step 2

D DB query would not happen

💡 Hint

Focus on the 'Service Result' column at step 3

Concept Snapshot

Service Layer Pattern in Express:
- Controller handles HTTP requests
- Calls Service Layer for business logic
- Service Layer calls Data Access Layer (DB)
- Keeps code organized and testable
- Controller sends response after service returns data

Full Transcript

In Express, the service layer pattern separates concerns by having controllers handle requests and responses, while the service layer contains business logic and data access calls. When a client requests user data, the controller calls the service layer method getUserById with the user ID. The service layer queries the database and returns the user object. The controller then sends this data as a JSON response. This pattern keeps code clean and easier to maintain by isolating responsibilities.

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