Connecting Express.js with MongoDB

# CHAPTER 11

Connecting Express.js with MongoDB #

1. Introduction #

2. Learning Objectives #

• Establish a connection to a MongoDB database.

• Define data schemas and compile them into Models using Mongoose.

• Perform asynchronous CRUD operations on a real database.

• Understand the benefits of using an ODM over raw queries.

3. Beginner-Friendly Explanation #

4. Step 1: Installing Mongoose #

npm install mongoose

5. Step 2: Establishing the Connection #

In index.js:

const express = require('express');
const mongoose = require('mongoose');
const app = express();

app.use(express.json()); // Essential for POST requests

// The Connection String (Localhost example)
const DB_URI = 'mongodb://localhost:27017/my_express_db';

// Connect to MongoDB asynchronously
mongoose.connect(DB_URI)
    .then(() => {
        console.log("MongoDB Connected Successfully!");
        // Only start listening AFTER the database is connected
        app.listen(3000, () => console.log("Server running on port 3000"));
    })
    .catch((err) => {
        console.error("Database connection failed:", err);
    });

6. Step 3: Designing a Schema #

Create a file: models/User.js

const mongoose = require('mongoose');

// Define the Blueprint
const userSchema = new mongoose.Schema({
    name: { type: String, required: true },
    email: { type: String, required: true, unique: true },
    age: { type: Number, default: 18 }
}, { timestamps: true }); // Automatically adds createdAt and updatedAt fields

// Compile the schema into a Model and export it
module.exports = mongoose.model('User', userSchema);

7. Step 4: Executing Database Queries (CRUD) #

In controllers/userController.js:

const User = require('../models/User');

// CREATE
const createUser = async (req, res) => {
    try {
        // Create a new instance of the User model using the request body
        const newUser = new User(req.body);
        
        // Save it to MongoDB
        await newUser.save();
        
        res.status(201).json({ status: "success", data: newUser });
    } catch (err) {
        res.status(400).json({ error: err.message });
    }
};

// READ ALL
const getUsers = async (req, res) => {
    try {
        // Find ALL users in the database
        const users = await User.find();
        res.status(200).json({ status: "success", data: users });
    } catch (err) {
        res.status(500).json({ error: err.message });
    }
};

// READ ONE
const getUserById = async (req, res) => {
    try {
        const user = await User.findById(req.params.id);
        if (!user) return res.status(404).json({ error: "User not found" });
        
        res.status(200).json({ status: "success", data: user });
    } catch (err) {
        res.status(500).json({ error: err.message });
    }
};

module.exports = { createUser, getUsers, getUserById };

8. Backend Workflow: Handling Promises #

9. Best Practices #

• Never Hardcode Credentials: In Step 2, we hardcoded mongodb://localhost.... If you are using MongoDB Atlas (the cloud version), that string contains your database password! Never type it directly into index.js. Always store the connection string in a hidden .env file.

10. Common Mistakes #

• Server Crashing on Invalid IDs: MongoDB uses a very specific 24-character string for its ObjectIDs (e.g., 5f8a...). If a client requests /api/users/123, Mongoose will crash your server because 123 is not a valid 24-character hex string. You must wrap your database calls in try/catch blocks (as shown in Step 7) so that if Mongoose throws a "CastError", your server catches it and returns a clean JSON error instead of completely shutting down.

11. Exercises #

1. 1. Look at the User schema in Step 3. What is the architectural benefit of adding the { timestamps: true } option to the Mongoose schema?

12. Coding Challenges #

• Challenge: Using Mongoose syntax, write the controller logic for a deleteUser function. It should use await User.findByIdAndDelete(req.params.id) and return a 200 OK JSON message upon success.

13. MCQs with Answers #

14. Interview Questions #

• Q: Explain why Node.js and MongoDB are frequently paired together (the "M" and "N" in the MERN stack). What is the underlying data structure they share?

• Q: What is a Schema in Mongoose, and why do we apply strict schemas to a database (MongoDB) that is natively "schema-less"?

15. FAQs #

16. Summary #

17. Next Chapter Recommendation #