Resultados de búsqueda para composition

Microservices must be composed to provide users with complex and elaborated functionalities. According to the decentralized nature of micro-services, choreographies is the most appropriate style to achieve such com-position. However, this style forces to distribute the flow logic of the com-position among the participating microservices making difficult its analysis and update. The Business Process Model and Notation (BPMN) provides a graphical notation widely used in academia and industry to specify business processes. Within the microservice composition context, this notation can be used to create the big picture of such compositions. However, this notation is usually considered in orchestration-based solutions, and orchestration can be a drawback to achieve the decoupling pursued by a microservice architecture. Therefore, in this demo paper we present the architectural solution and its realization in Java/Spring technology to support an approach that allows defining a microservice composition keeping the benefits of both composition mechanisms, i.e., orchestration and choreography. Specifically, the supporting tool allows 1) defining the microservice com-position in a BPMN model to have the big picture of the whole composition, which facilitates further analysis and maintenance when requirements change, and 2) splitting this BPMN model into fragments that are distributed among microservices in order to be executed by following an event-based choreography of BPMN fragments, which provide a high degree of de-coupling and independence to implement and maintain microservices. This composition approach is supported by a microservice architecture defined to achieve that both descriptions of a composition (big picture and split one) coexist.

This paper faces the challenge of defining a microservice composition approach that provides the benefits of orchestration and choreography composition mechanisms. The main goal is to 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. The modeling language used to create such centralized model is the one provided by the BPMN process diagram. In particular, we introduce a proposal that provides the possibility of 1) defining the microservice composition in a BPMN model to have the big picture of the whole composition, which facilitates further analysis and maintenance when requirements change, and 2) executing the BPMN model by following an event-based choreography to provide a high degree of decoupling and independence to implement and maintain microservices. To this end, the paper presents (1) a set of guidelines to create microservice compositions in BPMN models, split them into fragments, and distribute these fragments among microservices to be executed through an event-based choreography, (2) a microservice architecture defined to support the coexistence of the two descriptions of a composition (i.e., the big picture and the split one), and (3) tool support in order to implement the proposed microservice architecture in Java/Spring technology.

Web applications development involves managing a high diversity of files and resources like code, pages or style sheets, implemented in different languages. To deal with the automatic generation of custom-made configurations of web applications, industry usually adopts annotation-based approaches even though the majority of studies encourage the use of composition-based approaches to implement Software Product Lines. Recent work tries to combine both approaches to get the complementary benefits. However, technological companies are reticent to adopt new development paradigms such as feature-oriented programming or aspect-oriented programming.Moreover, it is extremely difficult, or even impossible, to apply these programming models to web applications, mainly because of their multilingual nature, since their development involves multiple types of source code (Java, Groovy, JavaScript), templates (HTML, Markdown, XML), style sheet files (CSS and its variants, such as SCSS), and other files (JSON, YML, shell scripts).We propose to use the Common Variability Language as a composition-based approach and integrate annotations to manage fine grained variability of a Software Product Line for web applications.In this paper, we (i) show that existing composition and annotation-based approaches, including some well-known combinations, are not appropriate to model and implement the variability of web applications; and (ii) present a combined approach that effectively integrates annotations into a composition-based approach for web applications. We implement our approach and show its applicability with an industrial real-world system.