On the Definition of Microservice Bad Smells

Code smells and architectural smells (also called bad smells) are symptoms of poor design that can hinder code understandability and decrease maintainability. Several bad smells have been defined in the literature for both generic architectures and specific architectures. However, cloud-native appli...

Full description

Saved in:
Bibliographic Details
Published inIEEE software Vol. 35; no. 3; pp. 56 - 62
Main Authors Taibi, Davide, Lenarduzzi, Valentina
Format Journal Article
LanguageEnglish
Published Los Alamitos IEEE 01.05.2018
IEEE Computer Society
Subjects
anti-pattern
antipattern
architectural smell
bad smell
Cloud computing
code smell
Interviews
Logic gates
Maintainability
microservice
Product development
Researchers
Service computing
Software architecture
Software development
Software engineering
Online AccessGet full text

Cover

More Information
Summary:Code smells and architectural smells (also called bad smells) are symptoms of poor design that can hinder code understandability and decrease maintainability. Several bad smells have been defined in the literature for both generic architectures and specific architectures. However, cloud-native applications based on microservices can be affected by other types of issues. In order to identify a set of microservice-specific bad smells, researchers collected evidence of bad practices by interviewing 72 developers with experience in developing systems based on microservices. Then, they classified the bad practices into a catalog of 11 microservice-specific bad smells frequently considered harmful by practitioners. The results can be used by practitioners and researchers as a guideline to avoid experiencing the same difficult situations in the systems they develop.
Bibliography:ObjectType-Article-1
SourceType-Scholarly Journals-1
ObjectType-Feature-2
content type line 14
ISSN:0740-7459
1937-4194
DOI:10.1109/MS.2018.2141031