3 ms·
As others have already pointed out, you don't need microservices to achieve a good modularization of your code. Then have each team work on a different module,
by danmaz74 11y ago
As others have already pointed out, you don't need microservices to achieve a good modularization of your code. Then have each team work on a different module, with clearly defined APIs between them. No need to separate them with HTTP calls.
- federico3 11y agoThe main benefit of microservices is that each team can deploy their service independently. This is really useful to reduce the level of required of interaction (and pressure) between teams.
- marcosdumay 11y agoIt may reduce development interaction, but it'll certainly turn testing into a nightmare. If you have teams that communicate badly, you'll need people specialized in deployment and assigning issues to them. That's not a good situation anyway, but it's the less worse of them.
- alexandercrohde 11y agoAgain, this is something that is independent of microservices. If you have a modular mono codebase then one team can easily deploy commits that only touch their module.