Software architectural patterns in practice: an empirical study

Kassab, Mohamad; Mazzara, Manuel; Lee, Joo Young; Succi, Giancarlo

doi:10.1007/s11334-018-0319-4

Cited by 17 publications

(8 citation statements)

References 14 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Nevertheless, we realized that addressing quality attributes is a major concern in the design of both non-MSA-based and MSA-based systems. The results of the surveys conducted by Kassab et al [119], Ameller et al [120] and our study show that some quality attributes (e.g., performance, availability and security) are the common interest to practitioners of both MSA-based and non-MSA-based systems. Kassab et al [119] found that the most relevant quality attributes from an architectural design point of view in practice are usability, performance, modifiability, and availability.…”

Section: Design Of Microservices Systemssupporting

confidence: 57%

“…The results of the surveys conducted by Kassab et al [119], Ameller et al [120] and our study show that some quality attributes (e.g., performance, availability and security) are the common interest to practitioners of both MSA-based and non-MSA-based systems. Kassab et al [119] found that the most relevant quality attributes from an architectural design point of view in practice are usability, performance, modifiability, and availability. Ameller et al [120] identified that the most important quality attributes for practitioners in service-based systems are dependability, performance, security, and usability.…”

Section: Design Of Microservices Systemssupporting

confidence: 57%

See 1 more Smart Citation

Design, Monitoring, and Testing of Microservices Systems: The Practitioners' Perspective

Waseem,

Liang,

Shahin

et al. 2021

Preprint

View full text Add to dashboard Cite

Context: Microservices Architecture (MSA) has received significant attention in the software industry. However, little empirical evidence exists on design, monitoring, and testing of microservices systems.Objective: This research aims to gain a deep understanding of how microservices systems are designed, monitored, and tested in the industry. Method:A mixed-methods study was conducted with 106 survey responses and 6 interviews from microservices practitioners. Results:The main findings are: (1) a combination of domain-driven design and business capability is the most used strategy to decompose an application into microservices, (2) over half of the participants used architecture evaluation and architecture implementation when designing microservices systems, (3) API gateway and Backend for frontend patterns are the most used MSA patterns, (4) resource usage and load balancing as monitoring metrics, log management and exception tracking as monitoring practices are widely used, (5) unit and endto-end testing are the most used testing strategies, and (6) the complexity of microservices systems poses challenges for their design, monitoring, and testing, for which there are no dedicated solutions. Conclusions:Our findings reveal that more research is needed to (1) deal with microservices complexity at the design level, (2) handle security in microservices systems, and (3) address the monitoring and testing challenges through dedicated solutions.

show abstract

Section: Design Of Microservices Systemssupporting

confidence: 57%

Section: Design Of Microservices Systemssupporting

confidence: 57%

Design, Monitoring, and Testing of Microservices Systems: The Practitioners' Perspective

Waseem,

Liang,

Shahin

et al. 2021

Preprint

View full text Add to dashboard Cite

show abstract

“…Considering the non-functional requirements and quality attributes like modifiability, maintainability, adaptability, and security, the framework architecture decisions [15] were taken to use micro-services. The advantages of micro-services can be characterized as the ease of maintainability, scalability, and cross-functional team maintenance.…”

Section: High-level Architecture Of the Systemmentioning

confidence: 99%

Analysis of Energy Consumption of Software Development Process Entities

et al. 2020

Self Cite

View full text Add to dashboard Cite

With the growing need for software-driven devices in modern life, the pervasive necessity of energy efficiency is also rising dramatically. Considering the importance of energy-efficient software in the IT-sphere, many companies started to search and uncover ways for minimizing energy loss. We study the software development process in terms of energy consumption. This depends on various factors that have to be monitored continuously. In this paper, we propose the Innometrics framework for monitoring the software development process and analyzing the profiles of energy consumption by user devices. The motivating idea of the project is to provide crucial insights and to clarify which development activities are the main drivers behind the energy consumption.

show abstract

“…Architectural patterns are part of the trend of knowledge based architecture design; Li et al (2013). Kassab et al (2018), Taibi et al (2018), and Harrison et al (2007) show how patterns are instrumental in the capturing of architectural design decisions. In this article, we describe such a pattern in detail and provide the design decisions that were employed in practice, with the goal of providing a comprehensive source of knowledge for practitioners.…”

Section: Introductionmentioning

confidence: 99%

An Empirical Characterization of Event Sourced Systems and Their Schema Evolution -- Lessons from Industry

Overeem,

Spoor,

Jansen

et al. 2021

Preprint

View full text Add to dashboard Cite

Event sourced systems are increasing in popularity because they are reliable, flexible, and scalable. In this article, we point a microscope at a software architecture pattern that is rapidly gaining popularity in industry, but has not received as much attention from the scientific community. We do so through constructivist grounded theory, which proves a suitable qualitative method for extracting architectural knowledge from practitioners. Based on the discussion of 19 event sourced systems we explore the rationale for and the context of the event sourcing pattern. A description of the pattern itself and its relation to other patterns as discussed with practitioners is given. The description itself is grounded in the experience of 25 engineers, making it a reliable source for both new practitioners and scientists. We identify five challenges that practitioners experience: event system evolution, the steep learning curve, lack of available technology, rebuilding projections, and data privacy. For the first challenge of event system evolution, we uncover five tactics and solutions that support practitioners in their design choices when developing evolving event sourced systems: versioned events, weak schema, upcasting, in-place transformation, and copy-and-transform.

show abstract

Software architectural patterns in practice: an empirical study

Cited by 17 publications

References 14 publications

Design, Monitoring, and Testing of Microservices Systems: The Practitioners' Perspective

Design, Monitoring, and Testing of Microservices Systems: The Practitioners' Perspective

Analysis of Energy Consumption of Software Development Process Entities

An Empirical Characterization of Event Sourced Systems and Their Schema Evolution -- Lessons from Industry

Contact Info

Product

Resources

About