2020
DOI: 10.1007/978-3-030-59592-0_6
|View full text |Cite
|
Sign up to set email alerts
|

Microservices Backlog - A Model of Granularity Specification and Microservice Identification

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
6
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
7
1

Relationship

2
6

Authors

Journals

citations
Cited by 12 publications
(6 citation statements)
references
References 19 publications
0
6
0
Order By: Relevance
“…The graph theory of design properties enables the direct analysis of coupling properties. Thirteen metrics have been proposed for measuring microservice coupling [35], [43], [44], [54], [59], [60], while fourteen metrics for service-oriented architecture (SOA) [28], [51], [58], [61]. Expressively, four of the proposed microservice metrics by Bogner et al [29] were derived from SOA metrics [53] in the context of microservice architecture.…”
Section: A Couplingmentioning
confidence: 99%
“…The graph theory of design properties enables the direct analysis of coupling properties. Thirteen metrics have been proposed for measuring microservice coupling [35], [43], [44], [54], [59], [60], while fourteen metrics for service-oriented architecture (SOA) [28], [51], [58], [61]. Expressively, four of the proposed microservice metrics by Bogner et al [29] were derived from SOA metrics [53] in the context of microservice architecture.…”
Section: A Couplingmentioning
confidence: 99%
“…The genetic algorithm considers coupling, complexity, semantic similarity and cohesion metrics to automatically distribute user stories to microservices. It tries to find the best combination and assignment of user stories to microservices, thus minimizing the granularity metric ( Vera-Rivera et al, 2020 ). It is important to note that semantics and conceptual similarity play a big role in several topics around architecture, including architecture recovery, refactoring ( e.g ., Feature Envy, Move Method, Extract Class), and design principles (single responsibility principle).…”
Section: Microservices Backlogmentioning
confidence: 99%
“…Their multimodel approach combines different independent models that represent a business process like control, data, and semantic dependencies [16]. Rivera et al [17] propose another intelligent and optimal method that works on user stories to decompose the functionalities or requirements of the application into microservices. Most of these existing approaches have two important disadvantages: 1) Lack of validation of the results and 2) Over dependency of their approach on expert opinion.…”
Section: Related Workmentioning
confidence: 99%