Service layer pattern in Express - Mini Project: Build & Apply

Building a Service Layer in Express

📖 Scenario: You are creating a simple Express app to manage a list of books. To keep your code clean and organized, you will use the Service Layer pattern. This means you will separate the logic that handles data from the code that handles HTTP requests.

🎯 Goal: Build an Express app with a service layer that manages book data. You will create the data, add a configuration variable, write the service logic to get books, and finally connect the service to an Express route.

📋 What You'll Learn

Create an array called books with three book objects, each having id, title, and author properties

Add a variable called maxBooks set to 3 to limit how many books the service returns

Create a service function called getBooks that returns books up to maxBooks

Set up an Express route /books that uses the getBooks service to send JSON response

💡 Why This Matters

🌍 Real World

Many web apps separate business logic from routing to keep code clean and reusable. Service layers help organize code for features like user management, product catalogs, or orders.

💼 Career

Understanding service layers is important for backend developers working with Express or similar frameworks. It shows good coding practices and prepares you for larger projects.

1

Create the initial book data

Create an array called books with these exact three objects: { id: 1, title: 'The Hobbit', author: 'J.R.R. Tolkien' }, { id: 2, title: '1984', author: 'George Orwell' }, and { id: 3, title: 'To Kill a Mockingbird', author: 'Harper Lee' }.

Express

// Create the books array with 3 book objects
// Your code here

Hint

Use const books = [ ... ] and include exactly three objects with the given properties.

2

Add a configuration variable

Add a variable called maxBooks and set it to 3. This will limit how many books the service returns.

Express

const books = [
  { id: 1, title: 'The Hobbit', author: 'J.R.R. Tolkien' },
  { id: 2, title: '1984', author: 'George Orwell' },
  { id: 3, title: 'To Kill a Mockingbird', author: 'Harper Lee' }
];

// Add maxBooks variable below
// Your code here

Hint

Use const maxBooks = 3; to create the variable.

3

Create the service function

Write a function called getBooks that returns the first maxBooks items from the books array using the slice method.

Express

const books = [
  { id: 1, title: 'The Hobbit', author: 'J.R.R. Tolkien' },
  { id: 2, title: '1984', author: 'George Orwell' },
  { id: 3, title: 'To Kill a Mockingbird', author: 'Harper Lee' }
];

const maxBooks = 3;

// Write getBooks function below
// Your code here

Hint

Define function getBooks() and return books.slice(0, maxBooks).

4

Connect service to Express route

Set up an Express app. Import express, create app with express(), and add a GET route /books that sends JSON response using the getBooks function. Finally, listen on port 3000.

Express

const books = [
  { id: 1, title: 'The Hobbit', author: 'J.R.R. Tolkien' },
  { id: 2, title: '1984', author: 'George Orwell' },
  { id: 3, title: 'To Kill a Mockingbird', author: 'Harper Lee' }
];

const maxBooks = 3;

function getBooks() {
  return books.slice(0, maxBooks);
}

// Import express, create app, add /books route using getBooks, and listen on port 3000
// Your code here

Hint

Use require('express'), create app, add app.get('/books', ...) route, and call app.listen(3000).

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