Closed evomimic closed 1 year ago
Multiple, smaller repositories enforces a cleaner separation of concerns, release independence for greater agility well-suited to a micro-services architecture. However, while the architecture is still in such flux, premature segmentation into repos based on a current understanding of the components can likely result in cross-repo re-factorings.
DECISION: For the prototype stage of development, we will stick with a mono-repo and a single workspace. However, to facilitate segmentation into different repos in the future, each DNA will have its own top-level folder.
Should we have different Github repos for each hApp, or a single repo?