ID Primary study,Proposal Type,DDD Purpose,Is Evaluated,Extraction,Comments
PS2,Procedure,Microservice identification,Yes," -  we are proposing a monolith decomposition procedure based on the refactoring strategy (Ivanov, N., & Tasheva, A. (2021). A Hot Decomposition Procedure, P. 3: 2246)

 - The procedure aims to make the transition to microservices gradually without downtime. (Ivanov, N., & Tasheva, A. (2021). A Hot Decomposition Procedure, P. 1: 767)

 - Step 2. Defining Bounded Contexts   (Ivanov, N., & Tasheva, A. (2021). A Hot Decomposition Procedure, P. 3: 3651)
","There are two main strategies for migration - re-creation and refactoring. (Ivanov, N., & Tasheva, A. (2021). A Hot Decomposition Procedure, P. 2: 3282)"
PS3,Framework,Microservice identification,Yes," - We provide a framework to transform the coupled components of the old system into independent components. This extraction of candidate of microservice based on DDD patterns static analysis (Joselyne, M. I., Bajpai, G., & Nzanywayingoma, F. (2021). A Sys, P. 1: 3714)
",None
PS5,Methodology,Microservice identification,Yes," - This section presents our model-driven methodology to derive microservice code from underspecified DDD domain models. (Rademacher, F., Sachweh, S., & Zundorf, A. (2020). Deriving Mic, P. 2: 5421)
",None
PS6,Reference architecture,Microservice architecture definition,No," - First we offer a conceptual domain model for software delivery processes and systems (Steffens, A., Lichter, H., & Döring, J. S. (2018). Designing a , P. 2: 4496)

 - The second contribution is a highly flexible microservice-based software architecture, which, based on our conceptual domain model and context map (Steffens, A., Lichter, H., & Döring, J. S. (2018). Designing a , P. 2: 5188)

 - The second contribution is a highly flexi-ble microservice-based software architecture, which, based on our conceptual domain model and context map, (PS-6 Steffens, A., Lichter, H., & Döring, J. S. (2018). Design, P. 2: 5188)","Te decision to clasificate it into frameworks comes from cites where they refer their contribution as a framework for example:

""Therefore, the approach provides an extensible framework to include more user support"" (Steffens, A., Lichter, H., & Döring, J. S. (2018). Designing a , P. 7: 2660) 

They don't have a study case to extract:

""Our approach has been implemented in a prototype called JARVIS and has been validated by conducting a small case study. The case study showed promising results like improving fast feedback on errors and a higher performance. Due to the limited space in this paper the case study could not be included."" (Steffens, A., Lichter, H., & Döring, J. S. (2018). Designing a , P. 7: 3076)
"
PS7,Reference architecture,Microservice architecture definition,No," - this paper proposes a design scheme of Web Platform Based on Domain Driven Design (Ding, Y., Wang, L., Li, S., Wang, X., & Zhang, J. (2020). Enter, P. 1: 1817)

 - this paper elaborates the architecture design based on the domain model in the platform and the application implementation method using the architecture, and  
finally provides a general software development architecture mode for the design of large-scale integrated platform. (Ding, Y., Wang, L., Li, S., Wang, X., & Zhang, J. (2020). Enter, P. 1: 2025)",None
PS8,Methodology,Microservice architecture definition,No," - We would extend the standard SEMAT Kernel by identifying additional alphas to deal with different aspects of Microservices practice foundation leveraging DDD (Daun, M. (2020). Extending the SEMAT Kernel for the practice of, P. 1: 2718)",None
PS10,Approach,Microservice architecture definition,Yes," - we propose a microservice migration approach based on the Strangler Fig  
pattern and Domain-Driven Design (DDD) to provide a complete architecture migration process and involving methods. (Li, C. Y., Ma, S. P., & Lu, T. W. (2020). Microservice Migratio, P. 1: 1119)
",None
PS12,Methodology,Microservice identification,Yes," - we propose a detailed methodology that uses DDD patterns to partition microservices, by respecting microservice architecture design and characteristics. (Josélyne, M. I., Tuheirwe-Mukasa, D., Kanagwa, B., & Balikuddem, P. 2: 1037)",None
PS14,Methodology,Microservice identification,No," - this study proposes the creation of Microservices of the Internet of Things (MicroloT), a methodology that allows the development of microservices-based applications. (Cabrera, E., Cardenas, P., Cedillo, P., & Pesantez-Cabrera, P. , P. 1: 3704)

 - It has seven stages: a) analysys of requirements, b) domain-driven delivery design, (Cabrera, E., Cardenas, P., Cedillo, P., & Pesantez-Cabrera, P. , P. 2: 2671)
","The concepts used in the b) stage comes from DDD, the reference [11] links the next site:
https://learn.microsoft.com/en-us/dotnet/architecture/microservices/microservice-ddd-cqrs-patterns/microservice-domain-model

Where Microsoft specify the use of DDD approach for developing microservices"
PS15,Approach,Microservice identification,Yes," - This paper presents a model-based approach for microservice architectural  
design and service integration through formal models using the UML and UML profiles. A domain model (bounded contexts) is used as a starting point (Chantamunee, S., Doung-in, S., Thanathamathee, P., Mahāwitthay, P. 1: 750)
","The study case for approach validation describes the approach steps itself, that's the reason why the example is consider the approach itself:

""For the exemplification of the approach, the domain of a taxi business is used"" (Chantamunee, S., Doung-in, S., Thanathamathee, P., Mahāwitthay, P. 1: 4841)
"
PS17,Framework,Data-intensive syatems definition,Yes," - we are developing and evaluating novel design guidelines to help practitioners safely architect data-intensive systems that have heterogeneous consistency requirements. Our guidelines are an advancement of Domain-Driven Design (DDD) [19] (Braun, S., Bieniusa, A., & Elberzhager, F. (2021, April 26). Ad, P. 1: 4947)

 - Note that our proposed replication framework cannot guarantee ACID durability (Braun, S., Bieniusa, A., & Elberzhager, F. (2021, April 26). Ad, P. 9: 2976)

 - We make use of practical examples and patterns described in code and UML [24] diagrams. Due to space limitations, we cannot provide these in this paper, but they are available in our GitHub repository [9]. (Braun, S., Bieniusa, A., & Elberzhager, F. (2021, April 26). Ad, P. 6: 3175)","The reason why this framework is related with microservices, is because their wuthors know that certain kinds of data communication errors are commonly made in microservices:

""If microservices replicate data from other microservices in order to be self-contained and independent of the availability of the other microservices, practitioners usually suggest having one dedicated microservice with the exclusive permission to execute updates on the replicated data. (Braun, S., Bieniusa, A., & Elberzhager, F. (2021, April 26). Ad, P. 3: 5392)
"
PS16,Reference architecture,Microservice architecture definition,No," - patterns are applied in this paper to develop a software architecture that is suitable for the deployment in the upcoming IIoT environments. (Dobaj, J., Krisper, M., Iber, J., & Kreiner, C. (2018, July 4)., P. 1: 1127)

 - The resulting microservice software architecture for the industrial Internet-of-Things is presented in Section 3. (Dobaj, J., Krisper, M., Iber, J., & Kreiner, C. (2018, July 4)., P. 2: 3426)

 - Pattern Solution. Define services corresponding to domain-driven design (DDD) subdomains (Dobaj, J., Krisper, M., Iber, J., & Kreiner, C. (2018, July 4)., P. 9: 3608)
",None
PS18,Approach,Define system's feature boundary,No," - The present work attempts to provide a novel approach to build emerging learning systems or frameworks by making use of both micro-services based software architectures and provisioning servers (Khemaja, M. (2016). Domain Driven Design and Provision of Micro, P. 1: 535)

 - Examples of bounded contexts (BC), goals (G), features (F)  capabilities (Ca) and possible related components (C) are illustrated in Table1 and classified accordingly to TLSs (Khemaja, M. (2016). Domain Driven Design and Provision of Micro, P. 3: 225)
","In the terminology section, they talk about Bounded context, and specify its functionality in the TLS (Target learnung system) to apply their approach.

The dddUsage categorization was decided according to the next sentence:

""Each feature should pertain to a unique bounded context hence delimiting its responsibility"" (Khemaja, M. (2016). Domain Driven Design and Provision of Micro, P. 3: 1279)"
PS21,Procedure,Find microservices,No," - this work presents the Service-oriented Process for Reengineering and DevOps—SPReaD, an instantiation of the mainstream SOA methodology focusing on the reengineering of legacy systems integrating DevOps aspects for developing microservices systems. (da Silva, C. E., Justino, Y. de L., & Adachi, E. (2022). SPReaD, P. 1: 1015)
",They are using DDD because as part of their method
PS22,Procedure,Microservice architecture definition,No," - this paper proposes a migration process based on SDLC, including all of the  
methods and tools required during design, development, and implementation (Fan, C. Y., & Ma, S. P. (2017). Migrating Monolithic Mobile App, P. 1: 1095)

 - In an attempt to overcome these difficulties, we migrated EasyLearn from the original monolithic architecture to a microservices system.  (Fan, C. Y., & Ma, S. P. (2017). Migrating Monolithic Mobile App, P. 2: 1735)

 - This process begins with analysis of the internal system architecture using Domain-Driven Design (DDD)  (Fan, C. Y., & Ma, S. P. (2017). Migrating Monolithic Mobile App, P. 2: 2624)
","(SDLC: software development life cycle)   (Fan, C. Y., & Ma, S. P. (2017). Migrating Monolithic Mobile App, P. 1: 929)

This proposal is ilustrated with an example in the same description of the procedure:
"" - The mobile application, EasyLearn, was used as an illustrative example"" (Fan, C. Y., & Ma, S. P. (2017). Migrating Monolithic Mobile App, P. 1: 1252)"
PS26,Reference architecture,Microservice architecture definition,No," - This work derived a reference architecture for MLOps in  
manufacturing based on identified manufacturing-specific  
requirements as well as generic MLOps capabilities (ps-26 Raffin, T., Reichenstein, T., Werner, J., Kühl, A., & Fra, P. 5: 2128)

 - In this context, DDD is especially suitable to identify so-called  
Core Domains that are vital for the success of the intended  
business success. Consequentially, this domain is prioritized in  
terms of development effort (ps-26 Raffin, T., Reichenstein, T., Werner, J., Kühl, A., & Fra, P. 5: 2775)

 - The edge device is the fundamental interface between OT  
and IT and employs an event-driven microservice architecture (ps-26 Raffin, T., Reichenstein, T., Werner, J., Kühl, A., & Fra, P. 4: 7040)
",None