Folder Structure

[mrmihi]

There are two options to go with,

1. Technical Role
2. Component

We can also try a mixture of both, but it will result in a nested folder structure of at least 2 levels from the root. Going component-based will offer much needed high-level overview of the project in a single glance. It also facilitates microservice architecture principles by only allowing components to communicate via their APIs. This will stop a dependency hell when developing, especially with novice developers like us.

Reference

[mrmihi]

We decided on doing it as a mix of both. At the frist layer we have component based folder and at the second layer we have technical roles based folders.