Node.js MVC directory structure example.

nodejs-directory-structure.md

Node.js MVC directory structure example.

├── app
│   ├── controllers
│   │   ├── admin
│   │   │   ├── posts.js
│   │   │   └── users.js
│   │   ├── posts.js
│   │   ├── session.js
│   │   └── users.js
│   ├── helpers
│   │   └── posts.js
│   ├── models
│   │   ├── post.js
│   │   └── user.js
│   └── views
│       ├── admin
│       │   └── posts
│       │       ├── edit.jade
│       │       ├── index.jade
│       │       └── new.jade
│       ├── layouts
│       │   └── application.jade
│       └── posts
│           ├── index.jade
│           └── show.jade
├── config
│   ├── application.js
│   ├── express.js
│   ├── middlewares
│   └── routes.js
├── lib
├── node_modules
├── package.json
├── public
│   ├── css
│   │   └── style.css
│   ├── img
│   │   └── logo.png
│   └── js
│       └── main.js
├── server.js
├── spec
│   ├── acceptance
│   │   ├── loginSpec.js
│   │   ├── postsSpec.js
│   │   └── signupSpec.js
│   ├── helper.js
│   └── models
│       ├── postSpec.js
│       └── userSpec.js
└── test

Is it recommended that both the Web-Server and the API-Server be in the same structure? Or should be coding as separate folders ? (node-web-server, node-api-server, etc.) Thanks...

Beautiful layout and just what I was looking for. Thanks!

Exactly what I was looking for. Thank you!

Thank you!

you might add service directory at the same level as controller , hence you will be able move your bussiness logic on this layer. you would have avoided decoupling or in the future if you would like to move your projects on different platforms such as serverless. it should facilitate this issue. instead of copying pasting bussiness logic . you could call service methods. as it separate from any protocol. it is sort of stand alone structure and abstracted .
we stumble upon this issue. we had to move some of our code on amazon lambda. thanks to this approach we were able to upload whole structure in a short time without dealing with huge problems