The pains and gains of microservices: A Systematic grey literature review

Abstract The design, development, and operation of microservices are picking up more and more momentum in the IT industry. At the same time, academic work on the topic is at an early stage, and still on the way to distilling the actual “Pains & Gains” of microservices as an architectural style. Having witnessed this gap, we set forth to systematically analyze the industrial grey literature on microservices, to identify the technical/operational pains and gains of the microservice-based architectural style. We conclude by discussing research directions stemming out from our analysis.

[1]  Michael Nygard,et al.  Release It!: Design and Deploy Production-Ready Software , 2017 .

[2]  Davide Taibi,et al.  On the Definition of Microservice Bad Smells , 2018, IEEE Software.

[3]  Alan Sill,et al.  The Design and Architecture of Microservices , 2016, IEEE Cloud Computing.

[4]  Klaus Krippendorff,et al.  Content Analysis: An Introduction to Its Methodology , 1980 .

[5]  Vahid Garousi,et al.  The need for multivocal literature reviews in software engineering: complementing systematic literature reviews with grey literature , 2016, EASE.

[6]  Thomas C. Fountain Web Service Oriented Architecture: "Smart Operations" and IT Strategy , 2003, ICWS.

[7]  Javad Ghofrani,et al.  Challenges of Microservices Architecture: A Survey on the State of the Practice , 2018, ZEUS.

[8]  Rami Bahsoon,et al.  Microservices and Their Design Trade-Offs: A Self-Adaptive Roadmap , 2016, 2016 IEEE International Conference on Services Computing (SCC).

[9]  Claus Pahl,et al.  Microservices: A Systematic Mapping Study , 2016, CLOSER.

[10]  Claus Pahl,et al.  Microservices: The Journey So Far and Challenges Ahead , 2018, IEEE Softw..

[11]  Antonio Brogi,et al.  Cloud Container Technologies: A State-of-the-Art Review , 2019, IEEE Transactions on Cloud Computing.

[12]  Philipp Schaer,et al.  Enhancing Visibility : Integrating Grey Literature in the SOWIPORT Information Cycle , 2008 .

[13]  Pooyan Jamshidi,et al.  Microservices Architecture Enables DevOps: Migration to a Cloud-Native Architecture , 2016, IEEE Software.

[14]  Evans,et al.  Domain-driven design , 2003 .

[15]  Vahid Garousi,et al.  Guidelines for including the grey literature and conducting multivocal literature reviews in software engineering , 2017, Inf. Softw. Technol..

[16]  Kai Petersen,et al.  Systematic Mapping Studies in Software Engineering , 2008, EASE.

[17]  Rainer Weinreich,et al.  Decision Models for Microservices: Design Areas, Stakeholders, Use Cases, and Requirements , 2017, ECSA.

[18]  Claes Wohlin,et al.  Experimentation in software engineering: an introduction , 2000 .

[19]  Patricia Lago,et al.  Research on Architecting Microservices: Trends, Focus, and Potential for Industrial Adoption , 2017, 2017 IEEE International Conference on Software Architecture (ICSA).

[20]  Tehmina N. Basit Manual or electronic? The role of coding in qualitative data analysis , 2003 .

[21]  Murat Koyuncu,et al.  A Systematic Literature Review on Microservices , 2017, ICCSA.

[22]  Olaf Zimmermann,et al.  Microservices tenets , 2017, Computer Science - Research and Development.