Hi guys.I have read that the preferred solution to organize project structure is structure it by components ( here ). I try to look at it from DDD perspective, so each aggregate root should have separated folder, contains individual services, model, controller etc. Am I right? Should I treat components as an aggregate root, or is it a bounded context or something else? What about communicating between components? How to achieve it? Sometimes there is a need to get data from another aggregate, how can I do it? I know that I can use an event to communicate between separated parts of an application, but sometimes a few aggregates should be orchestrated in one place, have you got a solution for it?I am a .Net Developer, so my perspective can be a little bit different than yours. I would like to start programming in Node professionally, but I feel that I need to understand how other people structuring their project and why. I know that very often it is personal preferences, but I see that a lot of apps have very plain architecture. I am used to writing a lot of boilerplate code to achieve very easy tasks, because every day I work on enterprise applications, so maybe because I see it a little bit different.I hope that I wrote it clearly to you and you will able to give me an answer.Thanks :)
Submitted April 17, 2019 at 09:54PM by Waryjot
No comments:
Post a Comment