TY - GEN
T1 - One Microservice per Developer
T2 - European Conference on Service-Oriented and Cloud Computing
AU - Amoroso d’Aragona, Dario
AU - Li, Xiaozhou
AU - Cerny, Tomas
AU - Janes, Andrea
AU - Lenarduzzi, Valentina
AU - Taibi, Davide
N1 - Publisher Copyright:
© IFIP International Federation for Information Processing 2023.
PY - 2023
Y1 - 2023
N2 - 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.
AB - 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.
U2 - 10.1007/978-3-031-46235-1_2
DO - 10.1007/978-3-031-46235-1_2
M3 - Conference contribution
AN - SCOPUS:85175872750
SN - 978-3-031-46234-4
T3 - Lecture Notes in Computer Science
SP - 19
EP - 34
BT - Service-Oriented and Cloud Computing - 10th IFIP WG 6.12 European Conference, ESOCC 2023, Proceedings
A2 - Papadopoulos, George A.
A2 - Rademacher, Florian
A2 - Soldani, Jacopo
PB - Springer
Y2 - 24 October 2023 through 25 October 2023
ER -