MicroART: A Software Architecture Recovery Tool for Maintaining Microservice-Based Systems

Abstract

General rightsCopyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights.• Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal Take down policyIf you believe that this document breaches copyright please contact us providing details, and we will remove access to the work immediately and investigate your claim.

Straddling the crevasse: A review of microservice software architecture foundations and recent advancements

“…The architectural pattern language developed by Richardson is a conglomeration of different patterns with defined relationships between them. Granchelli et al proposed tools for enabling the architecture of microservices . The MicroART tools employ model‐driven concepts and can be effectively used by the software architects .…”

An extensible data-driven approach for evaluating the quality of microservice architectures

“…The MicroQuality approach has been designed specifically for microservice-based systems. It combines the advantages of the approach for recovering microservice-based systems presented in [14] with the advantages of the extensible and generic approach assessing the quality of modelling artefacts published by Basciani et al [3]. On the one hand, a limitation of the scope of our approach to MSA lies in the fact that the used recovery approach relies on specific sources of information (e.g., Docker files) typically available only in microservice-based systems.…”

“…Listing 2: Metric Provider for complexity quality attribute Line 7 checks if the type specified in the quality model is instance of the processed element of the MSA Model in the iteration; if so, it applies the code responsible for computing the value of the metric on the current artefact (lines [8][9][10][11][12][13][14][15][16][17]. Once computed, it creates the relation in the resulting weaving model, to link the right artefact of the MSA model with the calculated value in the quality model (lines [14][15].…”

“…For what concerns abstraction, MicroQuality is centered around an architecture model of the system, allowing developers to focus explicitly on architecture-related concerns, instead of imposing the high cognitive burden due to the potentially highly heterogeneous technologies, the internal business logic of the involved microservices, their low-level details, etc. The architecture model of the system can be specified either manually or automatically via pre-existing architecture recovery techniques for MSAs (e.g., [2,14,15]). MicroQuality provides reusable quality attributes via an ecosystem of well-specified and languageindependent software quality attributes for MSAs; the proposed ecosystem fosters reuse by allowing developers to (i) define their own quality attributes, (ii) share them across different systems and organizations, and (iii) reuse quality attributes defined by other developers using the ecosystem.…”

Towards Micro Service Architecture Recovery: An Empirical Study

“…To the best of our knowledge the only study found in the literature that tackles architecture recovery in micro services is MicroART [25]. MicroART is the first prototype of an architecture recovery tool for micro service-based systems.…”