Does Domain-Driven Design Lead to Finding the Optimal Modularity of a Microservice?

Vural, Hulya; Koyuncu, Murat

doi:10.1109/access.2021.3060895

Cited by 20 publications

(12 citation statements)

References 39 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…C4: Validating our results quantitatively. Microservice implementation of some of the projects is available on Github (JPetStore 2 , TFWA 3 ). The remainder of the paper is organized as follows: Section 2 presents the related work going in the Greenfield decomposition domain.…”

Section: Figure 1 Modeling Options In Use Case Relationshipsmentioning

confidence: 99%

“…Related functionalities or requirements of the monolithic application are combined into a single business capability called microservice. This decomposition is based on the single responsibility principle that suggests "Gather together those functionalities that change for the same reason, and separate those that change for different reasons" [3]. This way MSA helps to handle complexities of bulky applications by breaking them into tiny services, where each service satisfies its own bounded-context.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

GreenMicro: Identifying Microservices From Use Cases in Greenfield Development

2022

View full text Add to dashboard Cite

Microservices architecture is a new paradigm for developing a software system as a collection of independent services that communicate through lightweight protocols. In greenfield development, identifying the microservices is not a trivial task, as there is no legacy code lying around and no old development to start with. Thus, identification of microservices from requirements becomes an important decision during the analysis and design phase. Use cases play a vital role in the requirements analysis modeling phases in a model-driven software engineering process. It is a technique of capturing high-level user functions and scope of the system. In this paper, we propose GreenMicro, an automatic microservice identification technique that utilizes the use cases model and the database entities. Both features are the artifacts of analysis and design phase that depict complete functionality of an overall system. In essence, a collection of related use cases indicates a bounded context of the system that can be grouped in a suitable way as microservices. Therefore, our approach GreenMicro clusters close-knit use cases to recover meaningful microservices. We investigate and validate our approach on an in-house proprietary web application and three sample benchmark applications. We have mapped our approach to state-of-the-art software quality assessment attributes and have presented the results. Preliminary results are motivating and the proposed methodology works as anticipated in producing functionally cohesive and loosely coupled microservice candidate recommendations. Our approach enables the system architects to identify microservice candidates at an early analysis and design phase of development.

show abstract

Section: Figure 1 Modeling Options In Use Case Relationshipsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%

GreenMicro: Identifying Microservices From Use Cases in Greenfield Development

2022

View full text Add to dashboard Cite

show abstract

“…Both projects were chosen because they provide a well-documented architecture and use many current technological standards and best practices. Despite not being real production systems, their maturity makes them a good alternative, also frequently used in other research studies [25][26][27].…”

Section: Case Studiesmentioning

confidence: 99%

Avoiding Excessive Data Exposure Through Microservice APIs

Genfer

Zdun

2022

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Data transfer and exchange of information through APIs are essential for each microservice architecture. Since these transfers often include private or sensitive data, potential data leaks, either accidentally or through malicious attacks, provide a high-security risk. While there are different techniques, like using data encryption or authentication protocols to secure the data exchange, only a few strategies are known to reduce the damage when an actual data breach happens. Our work presents a novel approach to identifying the optimal amount of data attributes that need to be exchanged between APIs and minimizes the damage in case of a potential breach. Our method relies only on static source code analysis and easy-to-calculate architectural metrics, making it well suited to be used in continuous integration and deployment processes. We further verified and validated the feasibility of our approach by conducting two case studies on open-source microservice systems.

show abstract

“…The eShopOnContainers 5 repository is Microsoft's reference implementation for microservice applications and, as such, has also been the subject of various research studies ( [2,31]). It provides several frontend clients for different platforms and four backend microservices plus additional infrastructure-related services.…”

Section: Case Study 2: Eshoponcontainersmentioning

confidence: 99%

Identifying Domain-Based Cyclic Dependencies in Microservice APIs Using Source Code Detectors

Genfer

Zdun

2021

Software Architecture

View full text Add to dashboard Cite

Isolation, autonomy, and loose coupling are critical success factors of microservice architectures. Unfortunately, systems tend to become strongly coupled over time, sometimes even exhibiting cyclic communication chains, making the individual deployment of services challenging. Such chains are highly problematic when strongly coupled communication e.g. based on synchronous invocations is used, but also create complexity and maintenance issues in more loosely coupled asynchronous or event-based communication. Here, cycles only manifest on a conceptual or domain level, making them hard to track for algorithms that rely solely on static analysis. Accordingly, previous attempts to detect cycles either focused on synchronous communication or had to collect additional runtime data, which can be costly and time-consuming. We suggest a novel approach for identifying and evaluating domain-based cyclic dependencies in microservice systems based on modular, reusable source code detectors. Based on the architecture model reconstructed by the detectors, we derived a set of architectural metrics for detecting and classifying domain-based cyclical dependencies. By conducting two case studies on open-source microservice architectures, we validated the feasibility and applicability of our approach.

show abstract

Does Domain-Driven Design Lead to Finding the Optimal Modularity of a Microservice?

Cited by 20 publications

References 39 publications

GreenMicro: Identifying Microservices From Use Cases in Greenfield Development

GreenMicro: Identifying Microservices From Use Cases in Greenfield Development

Avoiding Excessive Data Exposure Through Microservice APIs

Identifying Domain-Based Cyclic Dependencies in Microservice APIs Using Source Code Detectors

Contact Info

Product

Resources

About