~/nodejs/mongoose-mongodb-query-crud-operations-nodejs.md

Mongoose - Using CRUD operations in mongodb in nodejs

2 min readMay 06, 2020by Gorav Singal#mongodb#mongoose#nodejs
// TL;DR

Use Mongoose schemas and models to perform create, read, update, and delete operations on MongoDB collections from Node.js with a clean schema-based approach.

Mongoose - Using CRUD operations in mongodb in nodejs

MongoDB CRUD Operations

Mongoose provides a simple schema based solution to model your app-data. In this post, we will see how we can sue it to write basic CRUD operations in Nodejs.

Understanding Schema

First lets write a mongoose schema for a sample requirement. Example entity is Team, where I want to save:

  • Team name
  • Tem members and their roles
  • Who created this team
  • CreatedAt and UpdatedAt timestamps

JSON data

First lets take a look on how the JSON data will look like:

{
  name: "My Super Team",
  createdBy: "[email protected]",
  members: [
    {
      email: "[email protected]",
      role: "admin"
    },
    {
      email: "[email protected]",
      role: "user"
    },
    {
      email: "[email protected]",
      role: "admin"
    }
  ]
}

Lets write it in mongoose schema language.

'use strict';

const mongoose = require('mongoose');
const Schema = mongoose.Schema;
const timestamps = require('mongoose-timestamp');

const TeamMemberSchema = new Schema({
    email: String,
    role: String
});
TeamMemberSchema.plugin(timestamps);

const TeamSchema = new Schema({
    name: String,
    createdBy: String,
    members: [TeamMemberSchema]
}, {
    w: 'majority',
    wtimeout: 10000,
    collation: { locale: 'en', strength: 1 }
});

TeamSchema.plugin(timestamps);

module.exports = mongoose.model('Team', TeamSchema);

The model above is self explanatory. I have used a timestamp plugin for mongoose, which will automatically put two fields:

  • createdAt
  • updatedAt

Also, I have used a nested schema in above example. There is another important thing to see is that I have not defined _id field. Mongoose will automatically create this, if I have not mentioned it in my schema. I can also define how I would want my _id field to be generated.

Add New Record

add(args) {
    if (!args.name || !args.email) {
        return Promise.reject(new Error('Paass team name and creator email'));
    }
    //using winston logging
    logger.log('info', 'Adding team', {name: args.name, createdBy: args.email});

    let obj = new Team();
    obj.name = args.name;
    obj.createdBy = args.email;
    obj.members = [{
        email: args.email,
        role: args.role
    }];
    return obj.save();
}

Above code is pretty simple. You can add more robust checks, and error conditions. You might want to set data in cache.

Update Record

There are several ways you can update your record, it all depends on your need. Lets see few simple examples:

Simple update of a field

Say, we want to update team name.

By loading complete object

updateTeam(teamId, teamName) {
  return Team.findById(teamId)
    .then(team => {
      if (!team) {
        return Promise.reject(new Error('Team not found'));
      }
      team.name = teamName;
      return team.save();
    });
  return Team.upate({_id: args.teamId}, {
}

By NOT loading complete object

updateTeam(teamId, teamName) {
  return Team.upate({_id: args.teamId}, {
    name: teamName
  });
}

There are bunch of options to do update. You might want to see various options in mongoose documentation.

Get a Record

getById(teamId) {
  return Team.findById(teamId)
}

Delete Record

delete(teamId) {
  return Team.deleteOne({_id: teamId})
}

The examples above are simple and easy to understand. Let me know if if you have some comments.

$ subscribe --weekly

One deep dive a week, in your inbox

System design, AI engineering, trading systems and interview prep. Tested code, real numbers. Free, and you can unsubscribe any time.

or read it on gyanbyte.substack.com

Share

Related Posts

MongoDB with Mongoose — Patterns and Pitfalls

MongoDB with Mongoose — Patterns and Pitfalls

Schema Design Philosophy MongoDB schema design is fundamentally different from…

Nodejs - Json object schema validation with Joi

Nodejs - Json object schema validation with Joi

Introduction In this post, I will show how to validate your json schema…

How to check whether a website link has your URL backlink or not - NodeJs implementation

How to check whether a website link has your URL backlink or not - NodeJs implementation

Introduction I got my seo backlink work done from a freelancer. It was like 300…

How to connect to mysql from nodejs, with ES6 promise

How to connect to mysql from nodejs, with ES6 promise

Introduction I had to develop a small automation to query some old mysql data…

WebSockets with Socket.io in Node.js

WebSockets with Socket.io in Node.js

WebSocket vs HTTP Traditional HTTP follows a request/response model — the client…

Testing Node.js — Unit, Integration, and E2E

Testing Node.js — Unit, Integration, and E2E

Testing Strategy A solid testing strategy follows the testing pyramid — many…

Latest Posts

How to Stay Valuable as a Software Engineer in the AI Era: A Practical Playbook

How to Stay Valuable as a Software Engineer in the AI Era: A Practical Playbook

In the previous article I argued that AI is not killing software engineering…

How to Review AI-Generated Code: A Checklist for Catching What the Model Missed

How to Review AI-Generated Code: A Checklist for Catching What the Model Missed

A few months back I approved a PR that was almost entirely AI-generated. It…

How to Debug AI-Generated Code: Understand First, Fix Last

How to Debug AI-Generated Code: Understand First, Fix Last

In the last article I wrote about reviewing AI code before it goes in. This one…

The Future of Software Engineering: What AI Changes, What Stays, and Where the Jobs Go

The Future of Software Engineering: What AI Changes, What Stays, and Where the Jobs Go

Every few weeks somebody sends me a scary headline — “AI will replace all…

The Transactional Outbox Pattern: Never Lose an Event Again

The Transactional Outbox Pattern: Never Lose an Event Again

This is one of those patterns that looks like nothing until you get burnt once…

Event Sourcing, Explained: Store What Happened, Not Just the Final State

Event Sourcing, Explained: Store What Happened, Not Just the Final State

Here is a question I like to ask in interviews: your bank account shows a…