This is the first part of the series of articles on the Node.js framework known as NestJS, in this article we will see why and how to use NestJS.
...
For further actions, you may consider blocking this person and/or reporting abuse
Another option with Node+Express is github.com/TypedProject/ts-express...,
With TSED you don't need to create modules, so with NestJS it forces you to do it, which I don't understand and which makes the image put in Post look bad. Because with the controllers you have to create a module, while with TSED, you don't need that.
The reason for modules is, the framework is heavily inspired by Angular, and I can understand many Javascript developers are not used to such pattern, but it makes structuring large apps really easy.
It would be ideal if NestJS did not force you to create modules, that is to say to have the option to create them or not.
One thing that NestJS lacks is the deployment of their application.
Your diagram does not have Data Transfer Object(DTO) which is essential to have your Controller to validate(using class validator) before it gets to the Service Layer(which communicates to the Database).
Well, since it is just a "Getting Started" article, you might as well provide your DTO or the interface of that component in the next series.
Yeah I will cover them in upcoming articles, here they are not mandatory. So skipped from the diagram.