1. Beyond agile: is it time to adopt microsevices (2017), https://info.leanix.net/hubfs/leanIX_Microservices-Study.pdf
2. Balalaie, A., Heydarnoori, A., & Jamshidi, P. (2016). Microservices architecture enables devops: Migration to a cloud-native architecture. Ieee Software, 33(3), 42-52.
3. Knoche, H., & Hasselbring, W. (2019). Drivers and barriers for microservice adoption-a survey among professionals in germany. Enterprise Modelling and Information Systems Architectures (EMISAJ)-International Journal of Conceptual Modeling, 14(1), 1-35. [OpenAIRE]
4. L J., Fowler M. (2014) Microservices http://martinfowler.com/articles/microservices.html
5. Killalea, T. (2016). The hidden dividends of microservices. Communications of the ACM, 59(8), 42-45. [OpenAIRE]
6. Singleton, A. (2016). The economics of microservices. IEEE Cloud Computing, 3(5),16-20.
7. Erl, T. (1900). Service-oriented architecture. Pearson Education Incorporated.
8. Krafzig, D., Banke, K., & Slama, D. (2005). Enterprise SOA: service-oriented architecture best practices. Prentice Hall Professional.
9. MacKenzie, C. M., Laskey, K., McCabe, F., Brown, P. F., Metz, R., & Hamilton, B. A. (2006). Reference model for service oriented architecture 1.0. OASIS standard, 12(S 18).
10. Hasselbring, W. (2016, March). Microservices for scalability: keynote talk abstract. In Proceedings of the 7th ACM/SPEC on International Conference on Performance Engineering (pp. 133-134). [OpenAIRE]
International audience; This early work aims to allow organizations to diagnose their capacity to properly adopt microservices through initial milestones of a Microservice Maturity Model (MiMMo). The objective is to prepare the way towards a general framework to help companies and industries to determine their microservices maturity. Organizations lean more and more on distributed web applications and Line of Business software. This is particularly relevant during the current Covid-19 crisis, where companies are even more challenged to offer their services online, targeting a very high level of responsiveness in the face of rapidly increasing and diverse demands. For this, microservices remain the most suitable delivery application architectural style. They allow agility not only on the technical application, as often considered, but on the enterprise architecture as a whole, influencing the actual financial business of the company. However, microservices adoption is highly risk-prone and complex. Before they establish an appropriate migration plan, first and foremost, companies must assess their degree of readiness to adopt microservices. For this, MiMMo, a Microservices Maturity Model framework assessment, is proposed to help companies assess their readiness for the microservice architectural style, based on their actual situation. MiMMo results from observations of and experience with about thirty organizations writing software. It conceptualizes and generalizes the progression paths they have followed to adopt microservices appropriately. Using the model, an organization can evaluate itself in two dimensions and five maturity levels and thus: (i) benchmark itself on its current use of microservices; (ii) project the next steps it needs to achieve a higher maturity level and (iii) analyze how it has evolved and maintain a global coherence between technical and business stakes.