Florian Rademacher

Differences between Model-Driven Development of Service-Oriented and Microservice Architecture

Microservice Architecture (MSA) denotes a novel service-based architectural style with a strong focus on highly cohesive, loosely coupled services. A Microservice realizes a distinct architectural capability and exhibits a high degree of independence regarding development and operation. An alternative to MSA is the Service-oriented Architecture (SOA) style, which also leverages services as building blocks of distributed software systems. While MSA research is still formative, theoretical and practical aspects of SOA are being studied for more than a decade. Hence the question arises, in which areas and to what extent MSA research can draw on findings of SOA research. In this paper we address this question in the area of Model-driven Development (MDD), which has been intensively studied for SOA. Therefore, we identify conceptual and practical differences between SOA and MSA, and classify them on the basis of a hierarchical scheme. Starting from the identified differences we deduce implications on MDD of MSA and discuss them with respect to the existing body of knowledge of MDD of SOA. Hence, we provide an initial overview of differences between SOA and MSA, as well as implications in certain areas of MDD to consider when adapting service-oriented MDD to MSA.

MAGMA: build management-based generation of microservice infrastructures

Microservice architectures typically integrate a variety of loosely coupled infrastructure components. Due to technology heterogeneity, configuring them to provide the basis for a runnable service system might be time-consuming. Therefore, this paper presents MAGMA, a tool based on the Maven build management system that aims at accelerating the development of Microservice architectures by generating pre-configured, runnable systems. MAGMA enables the selective generation of infrastructure components like API Gateways and Service Discoveries, as well as the extension of existing Microservice architectures with customizable service templates and basic functional services.

Towards a UML Profile for Domain-Driven Design of Microservice Architectures

Domain-driven Design (DDD) is a model-driven approach to software development that focuses on capturing the application domain, its concepts and relationships in the form of domain models for architecture design. Among others, DDD provides modeling means for decomposing a domain into Bounded Contexts and expressing the relationships between them. With the recent emergence of Microservice Architecture (MSA), DDD again gains broad attention because a Bounded Context naturally maps to a Microservice, which enables the application of DDD for MSA design.

Design of a Domain-Specific Language Based on a Technology-Independent Web Service Framework

Nowadays web services gain more and more importance in allowing a standardized access to remote information without being tied to a specific form of presentation. The majority of such data interfaces is either based on the architectural REST style following World Wide Web specifications or the more protocol-oriented SOAP, which allows the definition of XML transfer structures.

AjiL: enabling model-driven microservice development

The development of microservice-based architectures typically involves tedious development tasks, e.g., to configure the necessary infrastructural components or to establish the interface-based communication between services. Therefore, this paper presents AjiL, a tool which aims to ease the necessary development effort with the means of graphical modeling and code generation. It comprises three major components: based on the lightweight Aji Modeling Language, the Aji Editor can create microservice system diagrams, which can be used by the Aji Spring Cloud Generator to generate system foundations.