raone1

8 ms·

1. 1.▲
   by raone1 4y ago

   Thanks for the suggestion.
2. 2.▲
   by raone1 4y ago

   I read somewhere that with larger teams, maintaining mono repo becomes harder because of merge conflicts. We are a small team and the codebase would not be that big.
3. 3.▲
   by raone1 4y ago

   Thanks. I now think that Mono would be a better choice. As we only do Integration and azure related stuff. So most of the code will be dependent on each other and reusable. Is it also better if we have to use some open source dependency at
4. 4.▲
   by raone1 4y ago

   We are going to do some Integration work, that may include Azure functions, servicebus, micro services and other stuff. We are creating some POCs for that and had a discussion about what approach to use. I have worked with multi repos and
5. 5.▲
   by raone1 4y ago

   Any particular reason??? I have read some blogs. But wanted to know from HN, what developers prefer.
6. 6.▲
   Ask HN: Mono Repo vs. Multi Repo?

   4 points by raone1 4y ago|13 comments
7. 7.▲
   Countries by Share of the Global Economy(visualcapitalist.com)

   1 points by raone1 4y ago|1 comments
8. 8.▲
   by raone1 4y ago

   Moved from Postman to Insomnia too. Postman was taking too much time to start and was very unresponsive compared to Insomnia, on my Work Laptop.