Abstract
In order to provide complex and elaborated functionalities, Microservices may cooperate with each other either by following a centralized (orchestration) or decentralized (choreography) approach. It seems that the decentralized nature of microservices makes the choreography approach more appropriate to achieve such cooperation, where lighter solutions based on events and message queues are used. However, orchestration through the usage of a process model makes it is easier to analyze the flow of the composition when modifications are required. In order to benefit from the goodness of these two approaches, this paper presents a hybrid solution based on the choreography of business process pieces, that are obtained from a previously defined description of the complete microservice composition. To support this solution, the EUCalipTool platform is presented.
Highlights
Companies such as Amazon, Airbnb, Twitter, Netflix, Apple, Uber, and many others have shifted towards a microservices architecture intending to be more agile in doing their business
We present the experiment that we have conducted to show the efficiency of our proposal in the development and evolution of microservice compositions
This section presents the experiment that we have conducted to show the efficiency of our proposal in the development and evolution of microservice compositions. This experiment aimed to compare the efficiency measurement obtained by a development based on EUCalipTool with the measurement obtained by an ad-hoc implementation of an event-based choreography
Summary
Companies such as Amazon, Airbnb, Twitter, Netflix, Apple, Uber, and many others have shifted towards a microservices architecture intending to be more agile in doing their business. The technology and functionality independence acquired when applying this architecture allows companies to replace, scale, and upgrade their applications and very fast (Newman, 2015; Bucchiarone et al, 2018; Shadija et al, 2017). To provide their customers with valuable services, developer teams are forced to build microservice compositions due to the small granularity level in which these operate (Dragoni et al, 2017). The major problem when creating compositions in this way is that their complexity grows, making more difficult their visualization, understanding, and maintenance This complexity has forced many companies to build their solution to compose microservices. To achieve microservices compositions we can find two major different approaches, these are choreography and orchestration
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
