Which has to stand as a damning indictment of the one-service-per-team model, surely? Something so inflexible can't survive contact with reality (for very long

Which has to stand as a damning indictment of the one-service-per-team model, surely? Something so inflexible can't survive contact with reality (for very long). At work we run 20-something microservices with a team of 14 engineers, and there's no siloing. If we need to add a feature that touches three services then the devs just touch the three services and orchestrate the deployments correctly. Devs wander between services depending on the needs of the project/product, not based on an arbitrary division.