Abstract
MS (microservice) has become the latest buzzword in software development. The MS approach to software development offers an alternative to the conventional monolith style. While benefits of MS-based development over monolith style are clear, industry experts agree that neither style provides an absolute advantage in all situations. Proponents contend that an MS approach to software development more readily facilitates mapping organizational changes manifesting from a more dynamic business environment to corresponding IT/IS (information technology/information systems) changes. This article identifies key challenges from the initial decision to adopt MSs to the ongoing task of sustaining the new paradigm over the long haul. It aims to provide insights to those considering MS-based software development.
Publisher
Association for Computing Machinery (ACM)
Reference30 articles.
1. Decomposition of Monolith Applications Into Microservices Architectures: A Systematic Review
2. Balalaie, A., Heydarnoori, A., Jamshidi, P. 2016. Microservices architecture enables DevOps: migration to a cloud-native architecture. IEEE Software 33(3), 42?52; https://dl.acm.org/doi/10.1109/MS.2016.64.
3. Towards Integrating Microservices with Adaptable Enterprise Architecture
4. How to transition incrementally to microservice architecture
5. Brown K. 2017. Apply the Strangler Fig application pattern to microservices applications. IBM; https://developer.ibm.com/articles/cl-strangler-application-pattern-microservices-apps-trs/.