Study ID,Architectural language,Objective,Based on
S1,An approach to evolve service-based architectures into microservice architectures.,"""an Architecture Description Language (ADL) is presented, which allows the modeling of service-based architectures, specifically SOA and MSA styles.""",C&C Views
S2,A data flow-driven approach that performs a systematic and easy-to-understand microservice-oriented decomposition.,"""tackle the challenges in migrating monolith to microservices architecture,""",DFD
S3,A new framework to build microservices-based software with the Software Product Line Engineering approach.,“We aim to minimize the effort in accommodating requirement changes by using the rigorous app- roach to variability management provided by SPLE”,None
S4,A novel approach to represent both the business processes and domain knowledge in a unified specification that could be transformed into boilerplate code compliant with Microservices architecture.,"“address the problems faced by businesses when creating scalable applications from ground-up, through an approach that allows developers to focus solely on the business logic”",None
S5,A monolith decomposition procedure based on the refactoring strategy.,"""help dealing with certain problems in systems and facilitate the decomposition into microservices""",None
S6,"4SRS-MSLA: An approach for designing a microservices-oriented logical architecture (MSLA), i.e., a logical view on the behavior of microservices and relationships between microservices.",“support a proper architecture design compliant with the microservices architecture main principles”,"DDD, SoaML, UML"
S7,"This reference architecture model consists of some key architectural components and building blocks, for implementing and managing microservices in the context of enterprise architecture within an organization.",“implementing and managing enterprise microservices in the context of enterprise Architecture.”,Enterprise Service Bus (EBS)
S8,A microservice composition approach based on the choreography of BPMN fragments.,"""provide a solution that allows developers to have a centralized model that describes the big picture of a microservice composition and also to have the possibility of executing the composition defined in this model through an event-based choreography""",BPMN
S9,A multi-level self-adaptation model for Microservice systems.,"""distinguish different self-adaptation requirements at different levels and provide corresponding methods to support multi-level self-adaptation""",None
S10,"A scalability pattern language to build highly scalable microservices-based systems, which organizes scalability patterns that were identified, organized, and categorized in a previous systematic study.","“highly scalable microservices-based systems, which organizes scalability patterns”",None
S11,A process model that focuses on and extends the design phase of the software development process.,"""A uniform process model can increase the standardization, common understanding and comparability of microservice identification approaches and architectures.""",None
S12,A routing mechanism to enhance the scalability of MSA-based applications consisting of stateful microservices.,“cope with scalability issues and demonstrated the viability of our approach through an experimental application”,DDD
S13,A proposed modernization framework of legacy application.,"""The overall objective of the proposed modernization framework is to provide guidelines on how to improve the current system.""",DDD
S14,A visual business process modelling language called VxBPMN4MS that is an extension of BPMN with support of variability for microservice compositions.,"""address the challenging issues of the development of adaptive microservice-based systems.""",BPMN
S15,An UML profile for microservices architectures that allows expressing the structural design of complex software systems according to microservices architectures through stereotypes and restrictions.,“allow expressing the structural design of complex software systems according to microservices architectures through stereotypes and restrictions”,"UML, MDE"
S16,An approach for continuously extracting the architecture of REST-based microservice software systems based on a combination of static service information.,“extract and analyze the architecture of a microservice-based software system based on a combination of static service information with infrastructure-related and aggregated runtime information”,None
S17,An approach to modeling microservice solutions based on CBDI SAE metamodel for SOA.,"""That approach gives modeling activities and relations between them, definitely points out which models may be built in each activity, and prescribes relations between the models and how to describe the models.""","CBDI-SAE metamodel for SOA, UML"
S18,A specification for allowing external applications to access the test parameters used to test the microservice.,"“The architecture proposed in this paper is designed to overcome the test challenges in microservices, more precisely performance tests.”",None
S19,A method for decomposition of the monolithic systems by identifying microservices automatically.,“transform existing applications into microservices using code repositories”,None (graph clusters)
S20,MicroQuality: A novel approach for the quality evaluation of microservice architectures.,"""MicroQuality has been architected so to enable the continuous quality assessment of MSAs in order to get data-driven and timely insights in the overall quality of the measured system.""",MDE
S21,An architectural conformance process for the microservice architecture.,"""We provide software architects with a multi-platform solution that allows (i) the verification of the structural design of each microservice and (ii) the restriction of communication between microservices.""",adapted from DCL (Dependency Constraint Language) language
S22,"A solution for managing the deployment of microservice-based applications using open-source solutions and industry standards, a modular CI/CD system was implemented, which has facilitated the design, implementation as well as future expansions and adaptations of the system.","""automate the software delivery process into a production environment, running the code through multiple automatically triggered steps without any intervention by humans.""",Pipes &filters view (Pipelines CI/CD)
S23,Automated attack graph generation relative to the development of microservice-based architectures,Help developers identify attack paths that comprise exploitable vulnerabilities in deployed services.,Attack graphs
S24,Declarative business processes to model and execute microservice orchestration from the perspective of data flow processes.,"""facilitate the modeling and execution of microservice orchestration"""," DSL, named Partitur"
S25,An interactive crossover service fusion approach based on microservice architecture.,"""This approach provides an overall solution for the rapid crossover service integration and helps to solve semantic inconsistencies that may exist in service integration""",None
S26,Decision guidance models for various areas of design in microservice architecture.,"""the developed models are intended to be used for identifying important requirements, for comparing different design options, for analyzing implications of a particular design, for identifying required system components, and for identifying and comparing di‚erent implementation technologies and their support for particular design options.""",None
S27,A Model-Driven methodology towards deriving microservice code from underspecified domain models.,"""systematically derive microservice code from underspecified domain models captured with Domain-driven Design (DDD).""","DDD, MDE, UML"
S28,A design of microservices using a message bus to decouple services communication.,"""this work purposes a decentralized message bus that helps to define how services communicate""",None
S29,A distributed service discovery mechanism.,"""ensures the strong consistency of data between cluster nodes, and improves the availability of service discovery.""",Raft algoritm
S30,"A layered Micro-service framework, and its overall architecture. ","""plit the traditional monomer application into a series of software service units that can be independently designed, developed, deployed, operated and maintained according to the business functions""",Layers
S31,"Schemas for pre-distribution of microservice, which are design pattern-based distribution and random distribution.","""a faster response time and less network calls for service execution.""",None
S32,An anomaly detection approach based on execution monitoring to detect faults automatically and locate the root causes of microservice application in a fine granularity.,"""detect faults automatically and locate the root causes of microservice application in a fine granularity""",None
S33,Discovery techniques that support the identification of suitable consumer-oriented parts of enterprise systems which could be reengineered as microservices based on the knowledge gained through business object relationships and their execution patterns,"""support the re-engineering of enterprise systems into microservices based on business objects and their relationships and associated operations with the coherent features and minimum communication overhead""",None
S34,A data-driven service discovery framework.,"""enables the creation of context-aware microservices architecture, able to allocate resources and replicate services in a federated environment.""",None
S35,"Fed-agent, a transactional layer acting as a proxy","""provide global consistency and ACID guarantees for multidatabase systems""",None
S36,An approach to transform a microservices-based architecture into a graph to extract metrics and key performance indicators (KPIs) to gain insight into the structure of this architecture.,"""Translating microservice architectures to graphs means representing services as vertices and connections as edges. Thus, graphs could be a meaningful description and visualization for microservices.""","DDD, graphs"
S37,GSMART is a novel approach to developing and operating microservice-based systems.,"""GSMART enables the parsing of microservice projects to produce SDGs for a microservice-based system. The resulting SDG makes it possible to visualize the system as a whole, thereby enabling the detection of anomalies, the tracing of service dependencies, and the selection of regression test cases.""",graphs
S38,A graph-based Root Cause Analysis framework.,"""a graph representation of the system is able to capture important information for RCA, like the topology of the architecture or the different connections, both logical and physical, between elements in the system.""",graphs
S39,"GMTA, A graph-based approach of trace analysis.","""understanding microservice architecture and diagnosing various problems""",graphs
S40,"A design of HT-RBAC model, which introduces a trust hierarchy able to operate across multi-domain of microservices.","""authenticate, authorize, and identify user’s access control via API-Gateway""",None
S41,A static analysis technique to identify microservices in a legacy software system based on topic models. ,"""microservice identification by resorting to topic modelling in order to identify services according to domain terms.""",None
S42,A systematic approach to identify microservices in early design phase.,"""to identify microservices which is based on use-case specification and functional decomposition of those requirements.""",None
S43,An interoperability tool for heterogeneous microservice systems that use different Pub/Sub technologies by providing two-way communication among them.,"""handle interoperability among microservice-based systems using message brokers as their Pub/Sub mechanism.""",None
S44,"A much simpler, human readable (not XML based) orchestration language. The LPMN engine that is capable to orchestrate the NLP microservices providing scalability capabilities.","""defining and running flexible workflows of language (like tagger, named entity recognizer, feature extractor) and machine learning tools (like clustering or classification).""",None
S45,A directed acyclic graph (DAG)-based model for describing microservice interdependencies.,"""A DAG-based model was used to abstract microservice interdependencies""",graphs
S46,A message exchange model for communication between LwM2M microservice replicas,"""This design can provide scalability and high availability to existing single machine-based LwM2M servers.""",Publication/Subscription
S47,Una metodología dividida por etapas que deben completar secuencialmente para transformar un monolito a microservicios.,"""realizar un mejor seguimiento de la integración continua para mejorar el aseguramiento de la calidad de los despliegues en producción de los microservicios,""","UML, DDD"
S48,Microns as the core architectural element in building microservices and other parts of the architecture. Microns are traditional commands that are further standardized in structure and behavior.,"""Using microns to build microservices makes it flexible to establish a service level objective for each service operation and not the entire service, thus accommodating for changing scalability, performance and security requirements.""",None
S49,Concepto de diseño para microservicios que abarca los retos que acompañan al elegir la arquitectura de microservicios.,"""consolidate the challenges and propose a conceptual design""",None
S50,"Microservices Backlog (MB), a model that allows software architects or development team to graphically analyze the microservices granularity. ","""graphically analyze the microservices granularity, starting from a set of functional requirements expressed as user stories within a product backlog (prioritized and characterized list of functionalities that an application must contain).""",None
S51,"A migration process based on SDLC, including all the methods and tools required during design, development, and implementation","""facilitate migration from a monolithic architecture to a microservice architecture.""",DDD
S52,A program analysis-based approach to migrate the monolithic legacy application to microservice architecture.,"""combining static and dynamic analysis on the application code or binary code to get the characteristics of the legacy monolith application.""",None
S53,An Extended approach to identify microservices from a set of business processes.,"""identify an independent collection of highly inter-related activities as microservices.""",BPMN
S54,"A behavioral microservice model in support of observability, allowing the description of runtime interactions within and between microservices and generated trace data.","""model microservices as observable execution paths. These serve as an abstraction for the reproducible generation of realistic trace data.""",None
S55,A collaborative modeling approach for MSA that relies on methods and techniques from the research area of Collaborative Model-Driven Software Engineering.,"""provide team collaboration means, e.g., partial imports or dependencies of other microservice models across teams.""",MDD
S56,A conceptual methodology to partition a microservice based on DDD.,"""Sizing microservices in this way allows for the creation of small and independent components, which have few operations that can be easily altered if possible.""",DDD
S57,MIcroservices COmposition (MICO) approach,"""MICO unifies and synergically combines the architectural, integration, and deployment aspects of MSA-based applications, enabling a “one-click” transition from modelled integration of microservices to running deployments.""",None
S58,"A composition method for semantic microservices where microservices are modeled as entity providers, in which a given microservice is responsible for managing individuals aligned with a predefined concept in a domain ontology.","""composing semantic microservices for achieving data integration based on Linked Data principles.""",OWL
S59,A scheme to refactor the existing SOA services found in the BPEL description into a set of microservices using decomposition pattern.,"""analyzing nouns in scenarios complying with a decomposition pattern proposed by Christ Richardson.""",Business Process Execution Language (BPEL)
S60,CSP# to analyze the realizability of microservice choreography under synchronous communication and asynchronous communication. CSP is a formal language for describing the interactions of concurrent and distributed systems.,"""use CSP# to analyze the microservice interaction contracts.""","CSP#, graphs"
S61,"An approach for combining structural, deployment, and run-time information about evolving microservices in one coherent space.","""generate an accurate representation of the evolving microservice-based system.""",None
S62,An ADL which is an extension of jADL. jADL is a formal ADL developed by the authors for describing static/dynamic/ mobile architectures to provide architects and various stakeholders the means to describe software systems.,"""describing a microservice architecture""","BPMN, jADL"
S63,UML profile that aims at enabling the modeling of Microservice systems by leveraging Domain-driven Design.,"""enables the expression of structural domain models as UML class diagrams by providing stereotypes and constraints for DDD patterns""","UML, DDD"
S64,An Ontology-Driven Conceptual Modelling approach based on the Ontology of Microservices Architecture Concepts (OMSAC) to describe MSAs in a holistic form. ,"""It allows representing MSA systems holistically or decomposed into individual viewpoints that meet different stakeholders’ specific information needs.""","OWL DL2, UML"
S65,An approach to building individual microservices in an emergent way.,"""yield a runtime search space of behavioural variation which machine learning can navigate at runtime to tailor the system to the current environment and client behaviour""",None
S66,Micro Service Architecture Recovery (MiSAR) uses a Model-Driven Engineering approach to generate architectural models of micro-service-based systems.,"""recover architectures of micro service systems."" and ""abstracts the concepts of a micro service architecture in a technology independent way, and mapping rules, which map an implemented micro service-based system into an architectural model which instantiates the metamodel.""",MDE
S67,An approach to analyzing an MSA for anti-patterns with tool support.,"""extracts relevant metrics and visualizations from dependency graphs by applying different graph algorithms. Our prime intention is to present an automated tool to analyze and identify anti-patterns that exist in an MSA system""",graphs
S68,GMAT (Graph-based Microservice Analysis and Testing) is an approach for assisting the development of an MSA-based system.,"""analyze and visualize the dependency relationships between microservices. GMAT could help developers to manage the complex service interactions and effectively find error roots when failures occur.""",graphs
S69,An approach to the Model-Driven Development of MSA-based software systems.,"""considers the different roles in a DevOps-based service team and identifies the types of models with which each role is concerned.""","MDD, UML"