Open renatojava opened 6 years ago
For simplicity, the book example application uses a mono repo.
While some developers use a mono repo, the 'standard' approach is to have a repo and a (e.g. Jenkins based) deployment pipeline per service along with other repositories for the shared libraries.
I plan to publish a a multi-repo version of the FTGO application in the very near future.
Hello,
I am reading your book and I have a doubt about the correct way of organizing the project. In this example, you create one big repo with all sources into, but when you have microservices and pipelines the correct way is not would be one repo per project?