#Management of nestjs project
1 messages · Page 1 of 1 (latest)
That's a broad question, you dont need all the fancy if your app requirements dont ask for it. Each ORM has their own up and downs so pick your poison. For monorepo tools nx seems to be the favourite from what I have seen. Regarding "structure" not that this matters to the final outcome -- put everything that changes together, together. You might like <#media message>
Thanks for the suggestions.
I'll implement and let you know.
Actually what I wanted was that is the structure where if I add some new feature or library the existing structure shouldn't get effected , in a way it is entirely independent from each other.
I didn't want to interfere with the rest of code or the directory structure in order to integrate a new feature.
@placid vine
Thats pretty much impossible, but you have the right mindset. Low coupling & high cohesion is what you are after.
can you guide me to do this.
or at least reach near
It'll be a great help. I am going through the resource that you have shared.
let me know when you are available. If you don't mind, can we have a call and discuss how to implement the above architecture.
in more detail.
No sorry. An architecture is driven by your app requirements and im not here to plan out an entire project for someone