Re:Ask HN: Why Not Microservices?
by sethammons on Thursday May 27, 2021 @07:00PM
(#27309670)
Microservices, in my experience, are chiefly about scaling teams (more freedom to move faster). In fewer cases, it is about optimizing a hot path. If it is not one of those, I'm having a hard time seeing why you would want the overhead of microservices.
[ Parent
| on HN ]
Re:Ask HN: Why Not Microservices?
by rajacombinator on Thursday May 27, 2021 @08:50PM
(#27310518)
Have you run into problems where it hinders team scaling by creating too much cross-team friction?
Re:Ask HN: Why Not Microservices?
by sethammons on Thursday May 27, 2021 @10:51PM
(#27311230)
The big issues we had were because we had different services reaching into and editing the same db tables in some cases. Re-architecting to have all data access via a new API (instead of direct DB access) across 13 services ran by 8 different teams across 2 business orgs has proven hard.
The other thing that can be a pain is due to rigid agile sprints. Need a change? Well that might get into their next sprint but there are probably other, higher priorities, so maybe next quarter. Or team A just does the work on team B’s service, and waits for code reviews and quality checks.