Catalog and detection techniques of microservice anti-patterns and bad smells: A tertiary study

Cerny, Tomas; Abdelfattah, Amr S.; Maruf, Abdullah Al; Janes, Andrea; Taibi, Davide

doi:10.1016/j.jss.2023.111829

Cited by 8 publications

(4 citation statements)

References 59 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…This can be reflected in the provided metrics, indicating that the E2E test might not achieve 100% coverage. This prompts the question of whether the remaining endpoints signify the presence of the Nobody Home smell [36], indicating missing wiring from the user interface, or if they represent outdated or dead code.…”

Section: Discussionmentioning

confidence: 99%

Test Coverage in Microservice Systems: An Automated Approach to E2E and API Test Coverage Metrics

Abdelfattah,

Cerny,

Yero

et al. 2024

Electronics

Self Cite

View full text Add to dashboard Cite

Test coverage is a critical aspect of the software development process, aiming for overall confidence in the product. When considering cloud-native systems, testing becomes complex, as it becomes necessary to deal with multiple distributed microservices that are developed by different teams and may change quite rapidly. In such a dynamic environment, it is important to track test coverage. This is especially relevant for end-to-end (E2E) and API testing, as these might be developed by teams distinct from microservice developers. Moreover, indirection exists in E2E, where the testers may see the user interface but not know how comprehensive the test suits are. To ensure confidence in health checks in the system, mechanisms and instruments are needed to indicate the test coverage level. Unfortunately, there is a lack of such mechanisms for cloud-native systems. This manuscript introduces test coverage metrics for evaluating the extent of E2E and API test suite coverage for microservice endpoints. It elaborates on automating the calculation of these metrics with access to microservice codebases and system testing traces, delves into the process, and offers feedback with a visual perspective, emphasizing test coverage across microservices. To demonstrate the viability of the proposed approach, we implement a proof-of-concept tool and perform a case study on a well-established system benchmark assessing existing E2E and API test suites with regard to test coverage using the proposed endpoint metrics. The results of endpoint coverage reflect the diverse perspectives of both testing approaches. API testing achieved 91.98% coverage in the benchmark, whereas E2E testing achieved 45.42%. Combining both coverage results yielded a slight increase to approximately 92.36%, attributed to a few endpoints tested exclusively through one testing approach, not covered by the other.

show abstract

Section: Discussionmentioning

confidence: 99%

Test Coverage in Microservice Systems: An Automated Approach to E2E and API Test Coverage Metrics

Abdelfattah,

Cerny,

Yero

et al. 2024

Electronics

Self Cite

View full text Add to dashboard Cite

show abstract

“…Major instances of technical debt include code smells and ineffective design decisions made by developers, which can have a negative impact on the maintainability, scalability, and quality of a software system [4]. Over the past few decades, research has heavily focused on the following areas [5]:…”

Section: Introductionmentioning

confidence: 99%

“…The problems that affect the overall quality of software, commonly referred to as code smells, can take the form of poorly designed architecture, hidden bugs, misuse of design patterns, or badly written code [4]. These code smells hinder the evolution of the software itself.…”

mentioning

confidence: 99%

Improving Code Smell Detection Using Deep Stacked Autoencoder

Rehef,

Abbas

2024

Preprint

View full text Add to dashboard Cite

The term "code smell" refers to an indication of a problem with the quality of source code. Numerous studies have been conducted to identify problematic features in source code. Initially, the focus was on utilizing metric-based and heuristic-based approaches. In recent years, however, there has been a shift towards using machine learning and deep learning (DL) techniques for smell detection. Nevertheless, the current algorithms are still considered to be in the early stages of development. Recognizing the challenges associated with identifying smells using DL methods, both academics and software developers have made efforts to address these obstacles. This work involves constructing and evaluating new DL models for code smell detection. Two models are built upon stacked autoencoders, employing a hybrid architecture that combines bidirectional long short-term memory and convolutional neural network components.

show abstract

“…From the available patterns, it is found that the circuit breaker pattern and the retry pattern was the widely implemented pattern due to its simplicity and efficient way of handling of failures. (3,4) These patterns are implemented either through method-based implementation or proxy-based implementation. These patterns are widely implemented for transient failure cases.…”

Section: Introductionmentioning

confidence: 99%

Performance of Dynamic Retry Over Static Towards Resilience Nature of Microservice

Punithavathy,

Priya

2024

IJST

View full text Add to dashboard Cite

Objectives: The main objective of this study is to enhance the flexibility of microservice-based cloud applications, so they can cope with transient or short-term failure conditions more effectively, providing a higher throughput of cloud applications as a result. Methods: The comparison is done between the existing or manual resilient patterns such as circuit breaker and retry with a dynamically proposed retry patterns using a microservice application. Findings: The short-term or transient failures in cloud based microservice applications can occur for many reasons. Examples such as Network glitches, service failures, timeouts of requests etc. These failures can bring down the entire application resulting in a cascading of failures. Resiliency patterns are used to protect these applications from failures. The widely used patterns are circuit breaker and retry, with static configurations. It is possible that the static configurations used in resiliency patterns might not support all types of failures. Hence, a dynamic approach has been proposed to satisfy all these transient failures of cloud. The analysis proves that the application efficiency is balanced in dynamic retry than the static configurations of resiliency pattern. Hence, performance can be increased up to 34.3%, which means the availability can be ensured, in transient failure cases. Very little research has been carried out on this resiliency pattern, and there are no standards available for this pattern. When comparing with the existing adaptive retry pattern the performance is increased up to 88.52%, while using a microservice application. Novelty: A dynamically modified resilient pattern is been proposed by incorporating additional parameters such as execution time to the existing parameters of the static retry pattern. This is an individual resilience pattern, which can perform independently when compared with other dynamic resilience patterns. Keywords: Dynamic retry, Request time, Static circuit breaker, Resilience, Static retry

show abstract

Catalog and detection techniques of microservice anti-patterns and bad smells: A tertiary study

Cited by 8 publications

References 59 publications

Test Coverage in Microservice Systems: An Automated Approach to E2E and API Test Coverage Metrics

Test Coverage in Microservice Systems: An Automated Approach to E2E and API Test Coverage Metrics

Improving Code Smell Detection Using Deep Stacked Autoencoder

Performance of Dynamic Retry Over Static Towards Resilience Nature of Microservice

Contact Info

Product

Resources

About