Hi @coolman1011
Answer to your First Question: Yes it is definitely worth it. Like you, I also preferred express and used it on a large scale project. Later on, things got built upon another thing and in the end, no matter how good I did the abstraction, there was chaos. I then shifted to NEST and it gave me a perfect MVC architecture.
Now to design a good module you should make sure that every module contains either a controller or a service and not both. For example if you are using a mysql db then you should create a DBModule containing DBService and then later call it in the modules containing the controllers using providers property.
Follow the DRY and SOLID principles and make the best out of the architecture.
Thanks.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
im very new to nest and just started learning it a few days ago..
is it worth it to use/switch to nest?
with express, i can easily create functions or controllers, etc
but with nest,
even i like the DI concept,
i found it takes lot more effort to develop a module
and how the hell do i design a good module LOL
Hi @coolman1011
Answer to your First Question: Yes it is definitely worth it. Like you, I also preferred express and used it on a large scale project. Later on, things got built upon another thing and in the end, no matter how good I did the abstraction, there was chaos. I then shifted to NEST and it gave me a perfect MVC architecture.
Now to design a good module you should make sure that every module contains either a controller or a service and not both. For example if you are using a mysql db then you should create a DBModule containing DBService and then later call it in the modules containing the controllers using providers property.
Follow the DRY and SOLID principles and make the best out of the architecture.
Thanks.