3 ms·
It’s depends on how you slice services. For one micro-service per a team I see benefits. On another end of the spectrum a single team managing 10-20 micro-servi
by citrin_ru 3y ago
It’s depends on how you slice services. For one micro-service per a team I see benefits. On another end of the spectrum a single team managing 10-20 micro-services with more than one service per developer. IMHO it creates more problems than solves. Also it is usually a waste of HW resources because a library call it is cheaper then a network request.
- whstl 3y agoI think it depends on more than that. A single team managing 10 microservices that actually make sense to be microservices (like the PDF renderer example above [1]) is kinda good and perfectly manageable. A team with one single microservice that would actually work better if it was part of a monolith is already in the "creates more problems than it solves" territory. [1] https://news.ycombinator.com/item?id=35812294 https://news.ycombinator.com/item?id=35812294