Day 55 of Learning MERN Stack

Hello Dev Community! 👋

It is officially Day 55 of my unbroken daily run toward mastering full-stack MERN engineering! Yesterday, I used the native MongoDB driver to run raw manual collections. Today, I completely standardized my data tier inside Prashant Sir's backend masterclass track by migrating to Mongoose ODM (Object Data Modeling)!

Instead of writing loose arrays or passing unvalidated fields, my backend now enforces strict structural blueprints right at the database layer.

🧠 Key Learnings From Node.js Lecture 29 (Mongoose Blueprints)

As captured inside my development file "Screenshot (126).png", using Mongoose transitions your data workflow from simple execution loops to strict schema modeling:

1. Enforcing Type Validation via mongoose.Schema

I replaced raw document inserts with a robust homeSchema. I defined precise configuration options like explicit datatypes (String, Number) and built-in enforcement checkers (require: true) to lock down bad data fields before they ever touch the database cluster:

javascript
const mongoose = require('mongoose');

const homeSchema = new mongoose.Schema({
    houseName: { type: String, require: true },
    price: { type: Number, require: true },
    location: { type: String, require: true },
    rating: { type: Number, require: true },
    photoUrl: String,
    description: String
});  homeSchema.pre('findOneAndDelete', async function(next) {
    const homeId = this.getQuery()._id;
    await favourite.deleteMany({ houseId: homeId });
    // Keeps the operational pipeline moving seamlessly
});