REST API Structure using NodeJS MongoDB (Mongoose)
Tags: node, mongodb, rest, api
Published: 2020-10-02 15:31:38

![Alt Text](https://dev-to-uploads.s3.amazonaws.com/i/zxvx4pk4tdlqyk1x2a4c.png)

### [UPDATE 2] New modified more robust structure with Generation Tool. Check out here [https://dev.to/sunilksamanta/calmapi-a-production-ready-rest-api-generator-using-nodejs-mongodb-pd9](https://dev.to/sunilksamanta/calmapi-a-production-ready-rest-api-generator-using-nodejs-mongodb-pd9)

### [UPDATE] There are structure improvements and addon features. Please follow the git repo for updated structure.

For each and every project I usually prefer using different architectures. It not just helps me explore new techniques but helps me make the next project better than before by applying the best of them and leave the worst.

Few months ago I found [this article](https://dev.to/pacheco/designing-a-better-architecture-for-a-node-js-api-24d) interesting. With writing a very minimum line of code you’ll get an API ready. I followed this structure and created my own with some customization and added basic modules and made it REST ready out of the box. The project features —

1. **Controller, Model & Service oriented architecture**

1. **Auth with JWT & Db Store**

1. **User Module**

1. **Post Module** (Sample CRUD)

1. **Media Upload**

1. **Centralized Http Response**

1. **Error Handler**

1. **.env support**

1. **Multi Environment config setup**

1. **Autobind Methods**

***If you’re too lazy to read further, here is the [github repo](https://github.com/sunilksamanta/node-mongoose-setup) for full project.***

{% github sunilksamanta/node-mongoose-setup %}

Lets dig into the Matrix..

## What we’re using?

1. NodeJS

1. MongoDB (Mongoose ODM)

## Directory Structure of the Project
```
       ├─ .env
       ├─ .gitignore
       ├─ config
       │  ├─ config.js
       │  ├─ database.js
       │  ├─ routes.js
       │  └─ server.js
       ├─ index.js
       ├─ package.json
       └─ src
          ├─ controllers
          │  ├─ AuthController.js
          │  ├─ Controller.js
          │  ├─ MediaController.js
          │  └─ PostController.js
          ├─ helpers
          │  ├─ HttpError.js
          │  ├─ HttpResponse.js
          │  └─ Utility.js
          ├─ models
          │  ├─ Auth.js
          │  ├─ Media.js
          │  ├─ Post.js
          │  └─ User.js
          ├─ routes
          │  ├─ auth.js
          │  ├─ index.js
          │  ├─ media.js
          │  └─ post.js
          └─ services
             ├─ AuthService.js
             ├─ MediaService.js
             ├─ PostService.js
             ├─ Service.js
             └─ UserService.js
```
## Lets talk about the structure

If you’ve already read the article where I found the struture then you’ve already understood what the structure does. If not please follow **[this link](https://dev.to/pacheco/designing-a-better-architecture-for-a-node-js-api-24d)** for better understanding of the basics of this architecture.

We have 2 base classes — One for Controller and another for Service.

1. **Controller.js** 

This base controller have the basic CRUD operations. To create a new controller just extend this base Controller class.

{% gist https://gist.github.com/sunilksamanta/a7560eda22e4c8477dbae088ac52683b %}

2. **Service.js**
 
This is the base Service class which includes the database operations. If you want to change the default behaviour of the services you can update this file.

{% gist https://gist.github.com/sunilksamanta/f87151f8cad11b501444f0c7def6b052 %}

## How to Create new CRUD Module?

If you want to create a new Module say Post. Then you’ll have to create 4 basic files. One Controller, one Service, one Model and one route file. And add the new route in routes/index.js with desired url.
There is a “Post” CRUD module included in this project for example.
```   
    controllers/PostController.js
    models/Post.js
    services/PostService.js
    routes/post.js
```
## Overriding Base class method

As an example if you see in the media Controller — the default delete method is overriden by its own class method as we have to delete the file from the file system also. So the overriden method is like bellow —
```
async delete(req, res, next) {
  const { id } = req.params;
  try {
      const response = await this.service.delete(id);
      // File Unlinking..
      if (response.data.path) {
          console.log("unlink item", response.data.path);
          fs.unlink(response.data.path, function (err) {
              if (err) {
                  console.log("error deleting file");
                  throw err;
              }
              console.log("File deleted!");
          });
      }
      return res.status(response.statusCode).json(response);
  }
  catch (e) {
      next(e);
  }
}
```
## Authentication

JWT authentication is added in this project. User model is defined in models/User.js. 
For Register, Login, Logout use these urls —
```
    [POST] api/auth/register
    [POST] api/auth/login
    [GET] api/auth/logout
```
Thats all for now.. If you need any help, I’ll love to do so.
Here is once again the git repo..

{% github sunilksamanta/node-mongoose-setup %}

## Want to contribute?

If you have any suggestion, feedback or you want to make this project more powerful — feel free to report issues or request a feature or suggest some changes. Fork and PR.

Happy Coding!

Originally published in medium -> [REST API Structure using NodeJS MongoDB (Mongoose)](https://medium.com/@sunilksamanta/rest-api-architecture-using-nodejs-mongodb-mongoose-64f9021c906f)