When developing and managing microservice systems, practitioners suggest that each microservice should be owned by a particular team. In effect, there is only one team with the responsibility to manage a given service. Consequently, one developer should belong to only one team. This practice of "one-microservice-per-developer" is especially prevalent in large projects with an extensive development team. Based on the bazaar-style software development model of Open Source Projects, in which different programmers, like vendors at a bazaar, offer to help out developing different parts of the system, this article investigates whether we can observe the "one-microservice-per-developer" behavior, a strategy we assume anticipated within microservice based Open Source Projects. We conducted an empirical study among 38 microservice-based OS projects. Our findings indicate that the strategy is rarely respected by open-source developers except for projects that have dedicated DevOps teams.

翻译：在开发和维护微服务系统时，从业者建议每个微服务应由特定团队负责。实际上，只有一个团队负责管理某个给定服务。相应地，每个开发者应仅属于一个团队。这种"每个开发者一个微服务"的做法在拥有庞大开发团队的大型项目中尤为常见。基于开源项目"集市式"软件开发模式——不同程序员如同集市上的商贩，各自协助开发系统的不同部分——本文探究我们能否观察到"每个开发者一个微服务"行为，这是我们认为在基于微服务的开源项目中预期会出现的一种策略。我们对38个基于微服务的开源项目进行了实证研究。研究结果表明，除拥有专职DevOps团队的项目外，开源开发者很少遵循该策略。