Exploration of academic and industrial evidence about architectural tactics and patterns in microservices

Osses, Felipe; Márquez, Gastón; Astudillo, Hernán

doi:10.1145/3183440.3194958

Cited by 16 publications

(5 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…The categorization and taxonomy of architectural patterns for microservices varies significantly in literature: Márquez and Astudillo [15] assigned 17 architectural patterns used in open-source projects to 11 groups while Valdivia et al [16] identified 54 patterns from white and grey literature and divided them into 6 groups. The taxonomy suggested by Osses et al [17] who reported 124 architectural patterns in the academic and industrial field has the greatest overlap with Microsoft's AAC. 8 of the 14 patterns in the AAC design and implementation category were also tagged as design patterns by Osses et al while another one occurs as a migration pattern.…”

Section: A Research Scopementioning

confidence: 99%

“…Osses et al [30] extracted 44 patterns and tactics used for microservices from 1,067 studies in a systematic review. In a related study [17], the authors focus on the intersection of patterns and tactics that have been described in academia as well as in industry. The authors found that most architectural patterns are associated with five quality attributes: scalability, flexibility, testability, performance, and elasticity.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Designing Microservice Systems Using Patterns: An Empirical Study on Quality Trade-Offs

Vale¹,

Correia²,

Guerra³

et al. 2022

Preprint

View full text Add to dashboard Cite

The promise of increased agility, autonomy, scalability, and reusability has made the microservices architecture a de facto standard for the development of large-scale and cloud-native commercial applications. Software patterns are an important design tool, and often they are selected and combined with the goal of obtaining a set of desired quality attributes. However, from a research standpoint, many patterns have not been widely validated against industry practice, making them not much more than interesting theories. To address this, we investigated how practitioners perceive the impact of 14 patterns on 7 quality attributes. Hence, we conducted 9 semi-structured interviews to collect industry expertise regarding (1) knowledge and adoption of software patterns, (2) the perceived architectural trade-offs of patterns, and (3) metrics professionals use to measure quality attributes. We found that many of the trade-offs reported in our study matched the documentation of each respective pattern, and identified several gains and pains which have not yet been reported, leading to novel insight about microservice patterns.

show abstract

Section: A Research Scopementioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Designing Microservice Systems Using Patterns: An Empirical Study on Quality Trade-Offs

Vale¹,

Correia²,

Guerra³

et al. 2022

Preprint

View full text Add to dashboard Cite

show abstract

“…Удобство обслуживания, надежность, эффективность и безопасность [19], [27], [28], [30], [35], [38]- [41] Отдельная серверная часть для каждого интерфейса / Backend for Frontend Совместимость и удобство обслуживания [18], [19], [30], [32], [35], [ Поскольку термины «паттерн проектирования» и «архитектурный паттерн» у авторов четко не различаются, некоторые паттерны были у них отнесены к обеим категориям, а в некоторых случаях проходили под общим названием «паттерн». Например, в категории просто паттернов были обнаружены разрешение непрерывной интеграции [19] и контейнер [19], [25].…”

Section: точка входа шлюз Api / Api Gatewayunclassified

“…Что касается микросервисной архитектуры, то, насколько нам известно, коллекции паттернов ограничены, поскольку микросервисы являются новым трендом. Однако мы можем найти исследования (например, [17][18][19] с многочисленными архитектурными паттернами, предоставляющими некоторый диапазон альтернатив. Среди них только в последней работе обеспечивается соответствие между атрибутами качества и паттернами.…”

Section: Introductionunclassified

Patterns Related to Microservice Architecture: a Multivocal Literature Review

Вальдивия¹,

Лора-Гонсалес²,

Лимон³

et al. 2021

Proceedings of ISP RAS

View full text Add to dashboard Cite

A Microservice Architecture enables the development of distributed systems using a set of highly cohesive, independent, and collaborative services, ready for current cloud computing demands. Each microservice can be implemented in different technologies, sharing common communication channels, which results in heterogeneous distributed systems that exhibit high scalability, maintainability, performance, and interoperability. Currently, there are many options to build microservices; some of them led by patterns that establish common structures to solve recurrent problems. Nevertheless, as microservices are an emerging trend, the relationship between quality attributes, metrics, and patterns is not clearly defined, which is a concern from a software engineering point of view, since such understanding is fundamental to correctly design systems using this architecture. This paper aims to extend the knowledge on the design of microservices-based systems by presenting a multivocal systematic literature review for microservices related patterns, tying them together with quality attributes and metrics, as can be found in academic and industry research.

show abstract

“…We consider the QAs and sub-QAs listed by ISO/ IEC 25010 standard as a reference point for our study. The necessary tactics required to achieve these QAs were derived by reviewing some standard software architectural reference books[4,2,36,16,2,22,25,31,6,29,38,13,3] and the information is stored in the form of structured tables available at https://doi.org/10.6084/ m9.figshare.14623005. Our ArchPatterns dataset is publicly shared at https://doi.org/10.6084/m9.figshare.14156408.2.…”

mentioning

confidence: 99%

Training Software Engineers for Qualitative Evaluation of Software Architecture

Kapur¹,

Kalra²,

Tiwari³

et al. 2021

Preprint

View full text Add to dashboard Cite

A software architect uses quality requirements to design the architecture of a system. However, it is essential to ensure that the system's final architectural design achieves the standard quality requirements. The existing architectural evaluation frameworks require basic skills and experience for practical usage, which the novice software architects lack.We propose a framework that enables novice software architects to infer the system's quality requirements and tactics using the software architectural block-line diagram. The framework does not assume any specific type of architectural diagrams. It takes an image as input, extracts various components and connections, and maps them to viable architectural patterns, followed by identifying the system's corresponding quality attributes (QAs) and tactics. The framework includes a specifically trained machine learning model based on image processing and semantic similarity methods to assist software architects in evaluating a given design by a) evaluating an input architectural design based on the architectural patterns present in it, b) lists out the strengths and weaknesses of the design in terms of QAs, c) recommends the necessary architectural tactics that can be embedded in the design to achieve the lacking QAs.To train our framework, we developed a dataset of 2,035 architectural images from fourteen architectural patterns such as Client-Server, Microservices, and Model View Controller, available at https://www.doi. org/10.6084/m9.figshare.14156408. The framework achieves a Correct Recognition Rate of 98.71% in identifying the architectural patterns with fourteen classes. We evaluated the proposed framework's effectiveness and usefulness by using controlled and experimental groups, in which the experimental group performed approximately 150% better than the controlled group. The experiments were performed as a part of the Masters of Computer Science course in an Engineering Institution.

show abstract

Exploration of academic and industrial evidence about architectural tactics and patterns in microservices

Cited by 16 publications

References 4 publications

Designing Microservice Systems Using Patterns: An Empirical Study on Quality Trade-Offs

Designing Microservice Systems Using Patterns: An Empirical Study on Quality Trade-Offs

Patterns Related to Microservice Architecture: a Multivocal Literature Review

Training Software Engineers for Qualitative Evaluation of Software Architecture

Contact Info

Product

Resources

About