8.2 KiB
8.2 KiB
type:: REVIEWS tags:: year:: 2024 venue:: SEAA full-title:: MicroArc Event Driven Analysis and Design Method for Microservice Based Systems date-start:: 21-06-2024 - 17:33 date-submitted:: external-links:: status:: DONE deadline-submission:: 21-06-2024 file:: @MicroArc: Event Driven Analysis and Design Method for Microservice Based Systems parent:: todoist:: https://app.todoist.com/app/task/80-ali-yildiz-and-onur-demirors-micro-arc-event-driven-analysis-and-design-metho-6VV8J9hJgcwQrj6c
- ### [[Highlights]]
-
- # Annotazioni
- (21/6/2024, 17:39:41)
- - “no de facto method for the analysis and design of systems within microservice architecture” ([Yildiz e Demirors, p. 1](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=1&annotation=EVJUEAD7)) #5fb236
- - “difficulties in developing microservice-based systems, owing to the lack of well-defined methodologies for analysis and design” ([Yildiz e Demirors, p. 1](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=1&annotation=5WDN4RWL)) #a28ae5
- - “analysis and design method for microservicebased systems.” ([Yildiz e Demirors, p. 1](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=1&annotation=2N9N6B7L)) #a28ae5
- - “new” ([Yildiz e Demirors, p. 1](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=1&annotation=848KS97R)) #ffd400
- *?? not so new, isn't it?*
- - “updated or changed, and the failure of the microservice does not affect the entire system.” ([Yildiz e Demirors, p. 1](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=1&annotation=72GBKSZB)) #5fb236
- - “The most obvious difference is to eliminate the coupling of objects, stop using the database for coordination, and enable asynchronous communication between services” ([Yildiz e Demirors, p. 1](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=1&annotation=KMJZP8F9)) #5fb236
- - “Organizations transitioning to software development using microservice architectures encounter challenges in distributing responsibilities and eliminating dependencies among developer teams.” ([Yildiz e Demirors, p. 2](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=2&annotation=KZ8VEY5L)) #5fb236
- - “Additionally, traditional analysis and design techniques have been found to be ineffective for microservice architectures” ([Yildiz e Demirors, p. 2](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=2&annotation=M5RU4YUH)) #5fb236
- - “MicroArc” ([Yildiz e Demirors, p. 3](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=3&annotation=ZPHTN5RA)) #5fb236
- - “BMC (Business Model Canvas), EPC (Event-driven Process Chain), and MCD (Microservices Communication Diagram).” ([Yildiz e Demirors, p. 3](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=3&annotation=LFPED24M)) #5fb236
- - “MicroArc is a method for analyzing and designing microservice-based systems that employs three modeling notations: the Business Model Canvas (BMC), Event-driven Process Chain (EPC), and Microservice Communication Diagram (MCD).” ([Yildiz e Demirors, p. 3](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=3&annotation=LDYMGINQ)) #ffd400
- *This is repeated.*
- - “Business Model Canvas (BMC)” ([Yildiz e Demirors, p. 3](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=3&annotation=HQMY5BRN)) #ffd400
- *This is from 2004*
- - “Key Activitie” ([Yildiz e Demirors, p. 3](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=3&annotation=56X5YLDE)) #5fb236
- - “Key Resources” ([Yildiz e Demirors, p. 3](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=3&annotation=T9ADBNQT)) #5fb236
- - “Key Partners:” ([Yildiz e Demirors, p. 3](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=3&annotation=M5SWSP6T)) #5fb236
- - “Key activities in BMC enable the elicitation of high-level requirements for the software that will be developed. Thus, rough boundaries about domains can be learned from key activities.” ([Yildiz e Demirors, p. 3](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=3&annotation=NK7XT82A)) #5fb236
- - “Event-Driven Process Chain (EPC)” ([Yildiz e Demirors, p. 3](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=3&annotation=9FJVBP9T)) #ffd400
- *This from 2000*
- - “It provides a high-level overview of how various components communicate and collaborate in a micro-service-based system.” ([Yildiz e Demirors, p. 4](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=4&annotation=G78JG3JA)) #ffd400
- - “In this study, an event-driven analysis and design method for microservice-based systems called MicroArc is presented. The goal is to analyze and design microservice-based systems in an event-driven manner. It comprises modeling notations and a guiding process to articulate how the method is applied. MicroArc allows transitions between models; therefore, integration between models can be established, and changes can be reflected in connected models. Using this approach, developers can identify events and microservice candidates by modeling the flow of processes in the early phase of development” ([Yildiz e Demirors, p. 6](zotero://select/library/items/LIUMGVSB)) ([pdf](zotero://open-pdf/library/items/3LW8QF7T?page=6&annotation=E36CCWEK)) #ffd400
- *The paper does not highlight the novelty of the proposed approach compared with the methodologies presented in the related work or with an existing baseline. The MicroArc methodologies rely on three different notations, BMC and EPC are existing languages developed a twe decades ago, and MCD, which seems to be conceived by the authors. None of the these languages have been discussed with existing languages, link BPMN. The evaluation of the methodology is not convincing as the authors discussed at a high level of abstraction the application of the approach on a case study. Said that, the paper cannot be accepted as it is, as it lacks details and discussions on the strenghts and limitations of the proposed languages with respect to existing notations and tools.*
- ### [[Comments]]
- Summary: The paper presents a methodology called MicroArc for developing microservice-based systems by means of three modeling notations: the Business Model Canvas (BMC), Event-driven Process Chain (EPC), and Microservice Communication Diagram (MCD). The application of the approach in a case study has also been discussed.
- Comments: While the paper is about an interesting and relevant topic, it does not sufficiently highlight the novelty of the proposed approach when compared with methodologies presented in related work or existing baselines. The MicroArc methodology relies on three different notations: BMC and EPC, which are established languages developed decades ago, and MCD, which appears to be introduced by the authors. However, there is no discussion on how these languages compare with existing ones, such as BPMN. Additionally, the evaluation of the methodology needs to be more convincing as the authors discuss the application of the approach at a high level of abstraction without providing detailed case studies or comparative analysis. Therefore, the paper cannot be accepted in its current form, as it lacks comprehensive details and discussions on the strengths and limitations of the proposed languages in comparison to existing notations and tools.
- ### [[REVIEWS/Notes]]
- ### YELLOW CONCERNS
background-color:: yellow
- {{query (and [[ffd400]] [[SEAA_2024_paper_80]] )}}
collapsed:: true
- ### ❓️Questions
- {{query (and [[question]] [[SEAA_2024_paper_80]] )[[question]]}}
query-table:: true
query-properties:: [:block]