Graphical and Textual Model-Driven Microservice Development

Rademacher, Florian; Sorgalla, Jonas; Wizenty, Philip; Sachweh, Sabine; Zündorf, Albert

doi:10.1007/978-3-030-31646-4_7

Cited by 24 publications

(33 citation statements)

References 18 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…In our previous works we developed LEMMA [60,63]. LEMMA is a set of Eclipse-based modeling languages and model transformations that aims to mitigate the challenges in MSA engineering (cf.…”

Section: Language Ecosystem For Modeling Microservice Architecturementioning

confidence: 99%

“…LEMMA's Domain Data Modeling Language [63] allows model construction in the context of the domain viewpoint on a microservice architecture. Therefore, it addresses the concerns of domain experts and microservice developers.…”

Section: Microservice Architecture Model Constructionmentioning

confidence: 99%

“…Fig. 1) because it provides them with a Java-aligned type system [63] given Java's predominance in service programming [9,67].…”

Section: Microservice Architecture Model Constructionmentioning

confidence: 99%

“…Second, we employ model-driven engineering (MDE) [13] to introduce a workflow for coping with the previously identified challenges in DevOps-based MSA engineering for SMOs. Third, we present and validate extensions to LEMMA (Language Ecosystem for Modeling Microservice Architecture), which is a set of Eclipse-based modeling languages and model transformations for MSA engineering [63] enabling sophisticated modeling support for the workflow.…”

Section: Introductionmentioning

confidence: 99%

See 3 more Smart Citations

Applying Model-Driven Engineering to Stimulate the Adoption of DevOps Processes in Small and Medium-Sized Development Organizations

et al. 2021

Self Cite

View full text Add to dashboard Cite

Microservice architecture (MSA) denotes an increasingly popular architectural style in which business capabilities are wrapped into autonomously developable and deployable software components called microservices. Microservice applications are developed by multiple DevOps teams each owning one or more services. In this article, we explore the state of how DevOps teams in small and medium-sized organizations (SMOs) cope with MSA and how they can be supported. We show through a secondary analysis of an exploratory interview study comprising six cases, that the organizational and technological complexity resulting from MSA poses particular challenges for small and medium-sized organizations (SMOs). We apply model-driven engineering to address these challenges. As results of the second analysis, we identify the challenge areas of building and maintaining a common architectural understanding, and dealing with deployment technologies. To support DevOps teams of SMOs in coping with these challenges, we present a model-driven workflow based on LEMMA—the Language Ecosystem for Modeling Microservice Architecture. To implement the workflow, we extend LEMMA with the functionality to (i) generate models from API documentation; (ii) reference remote models owned by other teams; (iii) generate deployment specifications; and (iv) generate a visual representation of the overall architecture. We validate the model-driven workflow and our extensions to LEMMA through a case study showing that the added functionality to LEMMA can bring efficiency gains for DevOps teams. To develop best practices for applying our workflow to maximize efficiency in SMOs, we plan to conduct more empirical research in the field in the future.

show abstract

“…In our previous works we developed LEMMA [60,63]. LEMMA is a set of Eclipse-based modeling languages and model transformations that aims to mitigate the challenges in MSA engineering (cf.…”

Section: Language Ecosystem For Modeling Microservice Architecturementioning

confidence: 99%

Section: Microservice Architecture Model Constructionmentioning

confidence: 99%

“…Fig. 1) because it provides them with a Java-aligned type system [63] given Java's predominance in service programming [9,67].…”

Section: Microservice Architecture Model Constructionmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

See 2 more Smart Citations

Applying Model-Driven Engineering to Stimulate the Adoption of DevOps Processes in Small and Medium-Sized Development Organizations

et al. 2021

Self Cite

View full text Add to dashboard Cite

show abstract

“…In this regard, Haselböck et al [8] identify five stakeholders profiles, which are software architect, developer, application engineering, quality assurer, and manager. Rademacher et al [9], on the other hand, identify three stakeholder roles, which are domain expert, service developer, and service operator. Descriptions of current microservice-based projects (such as [10] [11] [12]) also show that stakeholders participation is high in the modeling, design and analysis development phases, but low in the implementation phase, where technical experts and architects often make decisions.…”

Section: Introductionmentioning

confidence: 99%

Involving Stakeholders in the Implementation of Microservice-Based Systems: A Case Study in an Ambient-Assisted Living System

et al. 2021

View full text Add to dashboard Cite

A systematic gray literature review: The technologies and concerns of microservice application programming interfaces

2021

View full text Add to dashboard Cite

The microservice application programming interface (API) becomes a growing concern in the IT industry, as a result of the increasing usage of microservice architecture style. There exist many successful practices among companies, communities, and so on. In contrast, the related academic research is still at an early stage, where lacks an overview of technologies for the design, implementation and operation of microservice APIs, as well as a general picture of concerns. In this article, we try to fill this gap by eliciting the technologies and concerns on microservice APIs and establishing a microservice API description model, with the intention of aiding researchers to gain an overview of this field and find possible research directions, and helping practitioners to better understand microservice APIs and be aware of the existing approaches for daily work. Twelve academic papers and 38 gray literatures are selected and analyzed following the systematic literature review approach. Besides, we give our observations from this study. For researchers, our findings show the most cared concerns of practitioners, and our description model can be used as a reference for new theories, experiments, and future research dimensions. For practitioners, our study can be used as a guideline for microservices experimentation and a starting point for practice.

show abstract

Graphical and Textual Model-Driven Microservice Development

Cited by 24 publications

References 18 publications

Applying Model-Driven Engineering to Stimulate the Adoption of DevOps Processes in Small and Medium-Sized Development Organizations

Applying Model-Driven Engineering to Stimulate the Adoption of DevOps Processes in Small and Medium-Sized Development Organizations

Involving Stakeholders in the Implementation of Microservice-Based Systems: A Case Study in an Ambient-Assisted Living System

A systematic gray literature review: The technologies and concerns of microservice application programming interfaces

Contact Info

Product

Resources

About