Microservices in agile software development: a workshop-based study into issues, advantages, and disadvantages

@article{Taibi2017MicroservicesIA,
  title={Microservices in agile software development: a workshop-based study into issues, advantages, and disadvantages},
  author={Davide Taibi and Valentina Lenarduzzi and Claus Pahl and Andrea Janes},
  journal={Proceedings of the XP2017 Scientific Workshops},
  year={2017}
}
In the last years, cloud-native architectures have emerged as a target platform for the deployment of microservice architectures. The migration of existing monoliths into cloud-native applications is still in the early phase, and only few companies already started their migrations. Therefore, success and failure stories about different approaches are not available in the literature. This context connects also to the recently discussed DevOps context where development and continuous deployment… 
Processes, Motivations, and Issues for Migrating to Microservices Architectures: An Empirical Investigation
TLDR
This paper identifies a process framework based on the comparison of three different migration processes adopted by the interviewed practitioners, together with the common motivations and issues that commonly take place during migrations.
Towards defining a microservice migration framework
TLDR
This work proposes a work-plan to identify a decision framework that supports practitioners in the understanding of possible migration based benefits and issues that will lead to more reasoned decisions and mitigate the risk of migration.
Software components selection in microservices-based systems
TLDR
The goal is to support developers in selecting alternative components in case the component is not working anymore or future versions cannot be used in the future.
Agile architecture in the digital era: Trends and practices
The speed of response to change and fluidity are key preconditions for the next generation of IT solutions in the digital world. We are witnessing a rather unimaginable expansion of the use of
Contextual understanding of microservice architecture: current and future directions
TLDR
This work provides a detailed analysis of the differences between Service-Oriented Architecture (SOA) and Microservices, and describes both research and industry perspectives on the strengths and weaknesses of both architectural directions.
A curated Dataset of Microservices-Based Systems
TLDR
This paper shares a dataset, composed of 20 open-source projects, all using specific microservice architecture patterns, enabling researchers to compare results on common projects and believes that this dataset will be highly used by the research community for understanding more about microservices architectural and dependencies patterns.
A Qualitative Study of Architectural Design Issues in DevOps
TLDR
A mixed-methods study that consists of a qualitative case study of two teams in a company during their DevOps transformation and a content analysis of Stack Overflow and DevOps Stack Exchange posts to understand architectural design issues in DevOps reveals that being loosely coupled is one of the essential steps towards characterizing DevOps-driven architectures.
From Monolithic Systems to Microservices: A Decomposition Framework based on Process Mining
TLDR
A 6-step framework to reduce the subjectivity of the decomposition process is proposed and validated, in an industrial project, by comparing the proposed decomposition options with the one proposed by the software architect that manually analyzed the system.
A Decomposition and Metric-Based Evaluation Framework for Microservices
TLDR
The goal of the work is to provide a microservice measurement framework to objectively evaluate and compare the quality of microservices-based systems and to propose a decomposition system based on business process mining.
On the Definition of Microservice Bad Smells
TLDR
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 and classified the bad practices into a catalog of 11 micro service- specific bad smells frequently considered harmful by practitioners.
...
1
2
3
...

References

SHOWING 1-10 OF 24 REFERENCES
Applying SCRUM in an OSS Development Process: An Empirical Evaluation
TLDR
The results seem to show that SCRUM can be introduced and used in an ongoing geographically distributed Open Source Software process and that it helps control the development process better.
Comparing Requirements Decomposition Within the Scrum, Scrum with Kanban, XP, and Banana Development Processes
TLDR
Unexpectedly, decomposition techniques commonly adopted in traditional processes are still used in Agile processes, which may reduce project agility and performance and need to be addressed to a greater extent.
Comparing Communication Effort within the Scrum, Scrum with Kanban, XP, and Banana Development Processes
TLDR
This work compares the communication overhead and the different channels applied in three agile processes and in an unstructured process and finds that face-to-face communication is most frequently employed in the teams.
Interoperability-Related Architectural Problems and Solutions in Information Systems: A Scoping Study
TLDR
This research extracted a number of architectural interoperability problems and before-release solutions of interoperability on its different levels in information systems, and explored the interoperability metrics and research methods used to evaluate identified solutions.
A Continuous Software Quality Monitoring Approach for Small and Medium Enterprises
TLDR
An approach to allowSMEs to access SQA practices, using an SQA approach based on a continuous issue and error monitoring and a recommendation system that will suggest quality practices, so as to help SMEs to maintain quality above a minimum threshold.
Functional Size Measures and Effort Estimation in Agile Development: A Replicated Study
TLDR
This work replicated the original study twice, applying an exact replication to two plain Scrum development processes, and showed that the accuracy of the effort estimated by the developers is very accurate and higher than that obtained through functional size measures.
Studying Software Engineers: Data Collection Techniques for Software Field Studies
TLDR
A taxonomy of techniques is provided, focusing on those for data collection, organized according to the degree of human intervention each requires, and a discussion of how to use it effectively is provided.
Service Migration Patterns -- Decision Support and Best Practices for the Migration of Existing Service-Based Applications to Cloud Environments
TLDR
An implementation of the approach, which has been used to migrate a web-application stack from Amazon Web Services to the T-Systems cloud offering Dynamic Services for Infrastructure (DSI), and a methodology how these patterns should be applied during the migration of a service-based application or multiples thereof are presented.
MVP Explained: A Systematic Mapping Study on the Definitions of Minimal Viable Product
TLDR
A positive improvement of the state of the art of MVP and the definition of Minimum is found, related to technical characteristics of the product as well as market and customer aspects.
A Dynamical Quality Model to Continuously Monitor Software Maintenance
TLDR
An approach to continuously monitor the software operated by end users, automatically collecting issues and recommending possible fixes to developers and providing each company with a tailored SQA model, automatically obtained from companies’ bug/issue history is proposed.
...
1
2
3
...