Microservice-Aware Static Analysis: Opportunities, Gaps, and Advancements
Cerny, Tomas; Taibi, Davide (2023-12-19)
19.12.2023
Tomas Cerny and Davide Taibi. Microservice-Aware Static Analysis: Opportunities, Gaps, and Advancements. In Joint Post-proceedings of the Third and Fourth International Conference on Microservices (Microservices 2020/2022). Open Access Series in Informatics (OASIcs), Volume 111, pp. 2:1-2:14, Schloss Dagstuhl - Leibniz-Zentrum für Informatik (2023), https://doi.org/10.4230/OASIcs.Microservices.2020-2022.2
https://creativecommons.org/licenses/by/4.0/
© Tomas Cerny and Davide Taibi; licensed under Creative Commons License CC-BY 4.0.
https://creativecommons.org/licenses/by/4.0/
© Tomas Cerny and Davide Taibi; licensed under Creative Commons License CC-BY 4.0.
https://creativecommons.org/licenses/by/4.0/
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:oulu-202401221402
https://urn.fi/URN:NBN:fi:oulu-202401221402
Tiivistelmä
Abstract
Microservice architecture is the mainstream to fuel cloud-native systems with small service sets developed and deployed independently. The independent nature of this modular architecture also leads to challenges and gaps practitioners did not face in system monoliths. One of the major challenges with decentralization and its independent microservices that are managed by separate teams is that the evolving system architecture easily deviates far from the original plans, and it becomes difficult to maintain. Literature often refers to this process as system architecture degradation. Especially in the context of microservices, available tools are limited. This article challenges the audience on how static analysis could contribute to microservice system development and management, particularly managing architectural degradation. It elaborates on challenges and needed changes in the traditional code analysis to better fit these systems. Consequently, it discusses implications for practitioners once robust static analysis tools become available.
Microservice architecture is the mainstream to fuel cloud-native systems with small service sets developed and deployed independently. The independent nature of this modular architecture also leads to challenges and gaps practitioners did not face in system monoliths. One of the major challenges with decentralization and its independent microservices that are managed by separate teams is that the evolving system architecture easily deviates far from the original plans, and it becomes difficult to maintain. Literature often refers to this process as system architecture degradation. Especially in the context of microservices, available tools are limited. This article challenges the audience on how static analysis could contribute to microservice system development and management, particularly managing architectural degradation. It elaborates on challenges and needed changes in the traditional code analysis to better fit these systems. Consequently, it discusses implications for practitioners once robust static analysis tools become available.
Kokoelmat
- Avoin saatavuus [38841]
Ellei muuten mainita, aineiston lisenssi on https://creativecommons.org/licenses/by/4.0/