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.