Project structure by feature

[AguGriguol]

Hello!

I want to know what is the best structure for large node js projects, I've been thinking a lot about how to scale the project. If the project starts to grow up, maybe we'll have a lot of files in the services and routes folder. Would you consider grouping each feature in folders and inside of them put the services and routes? For instance,

--> user --> services --> routes --> test

Thanks in advance.

[nandanraj56]

Hi, I also have same question, currently when following microservice architecture, we have these service and tests files in their each repo, So its same as having multiple services, tests etc files each in its feature folder.

But in case of a monolithic architecture which way is more scalable and manageable? I wonder

Also a point to note is that angular by default keeps all files(controller, views and test) in respective components folder, the dont have a test folder which have all tests for all components. To me it makes more sense to have this way,

I want to know other developers view too...

[santiq]

Hi guys @AguGriguol @nandanraj56

My intention was never to say "use this way of separate folders" it is clear that separation by components has its advantages.

My main idea with this project was to teach about separation of concerns and clearly distinguish between layers.