Research on Architecting Microservices: Trends, Focus, and Potential for Industrial Adoption

Abstract

Abstract-Microservices are a new trend rising fast from the enterprise world. Even though the design principles around microservices have been identified, it is difficult to have a clear view of existing research solutions for architecting microservices.In this paper we apply the systematic mapping study methodology to identify, classify, and evaluate the current state of the art on architecting microservices from the following three perspectives: publication trends, focus of research, and potential for industrial adoption. More specifically, we systematically define a classification framework for categorizing the research on architecting microservices and we rigorously apply it to the 71 selected studies. We synthesize the obtained data and produce a clear overview of the state of the art. This gives a solid basis to plan for future research and applications of architecting microservices.

Execution of UML models: a systematic review of research and practice

“…We expected this result since model interpretation allows designers to achieve a high level of flexibility, which is more naturally achieved when abstract, platform-independent aspects are considered (rather than, e.g., hardware-specific ones). Nevertheless, given the continuously growing trend of cloud-and container-based solutions [15,16], we may expect that, in the future, interpretation of UML models will consider also platform-and hardwarerelated aspects of the system (e.g., for allowing the system to adapt its structure and behavior at runtime depending on the currently available infrastructural resources).…”

“…Note that most tools (16/19) heavily exploit Java, while most academic solutions (41/63) leverage technologies specifically developed for model manipulation (i.e., model transformation languages). Among them, QVT, 15 Acceleo, 16 and ATL. 17 Model-level interactive debugging This parameter specifies whether the analyzed solution provides some level of support for interactive debugging at the level of the source UML model (e.g., support for specifying breakpoints in the models, step-by-step execution at the UML level.).…”

“…12e, only a few solutions (21/82, of which 13 are tools) 14 Note that one approach can provide both translational and interpretive mechanisms (e.g., for code generation and model simulation, respectively). 15 http://www.omg.org/spec/QVT/. 16 https://eclipse.org/acceleo/.…”

From Monolith to Microservices: A Classification of Refactoring Approaches

“…However, the practical applicability is limited due to its dependence on a "detailed and exhaustive specification of the system" [4]. Microservices architecture as a field "rooted in practice" [16] is widely discussed in industry. It can be expected that further research will very likely reveal new approaches that can be incorporated and thus extend the findings of this study.…”

“…Several publications discussing Microservices also cover the aspect of migrating monoliths to Microservice-based architectures to some extent [22,25,29,36], but the topic is still evolving. A systematic mapping study conducted in 2016 identified 3 out of 21 studies dealing with migration topics [31], while Di Francesco et al found 16 out of 71 migrationrelated studies during their review in 2017 [16]. The papers found were mainly solution proposals, followed by experience reports and opinion papers.…”