2020 26th Conference of Open Innovations Association (FRUCT) 2020
DOI: 10.23919/fruct48808.2020.9087389
|View full text |Cite
|
Sign up to set email alerts
|

Fault Tolerant Central Saga Orchestrator in RESTful Architecture

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
4
0

Year Published

2020
2020
2023
2023

Publication Types

Select...
4
4

Relationship

0
8

Authors

Journals

citations
Cited by 9 publications
(4 citation statements)
references
References 7 publications
0
4
0
Order By: Relevance
“…4. In conclusion, to guarantee the versatility and robustness of the architecture, three aspects are important to take into account: (i) scalability, microservices can be scaled individually when running a heavy workload just by replicating them on several containers without and not replicating the others underutilized (maximize the performance with minimal cost) [19], [74]; (ii) communication in a microservice, is important establishing simple communication protocol like http, httprest "request/response" (synchronous protocol) or mqtt "publish/subscribe" (asynchronous protocol), depending on needs [67]; (iii) fine-grained microservices, it is fundamental to decompose each service focused on a specific function and of limited influence, according to the established requirements [75]; otherwise, this architecture suffers from a high level of abstraction and coordination among the teams [67], [76].…”
Section: Discussionmentioning
confidence: 99%
“…4. In conclusion, to guarantee the versatility and robustness of the architecture, three aspects are important to take into account: (i) scalability, microservices can be scaled individually when running a heavy workload just by replicating them on several containers without and not replicating the others underutilized (maximize the performance with minimal cost) [19], [74]; (ii) communication in a microservice, is important establishing simple communication protocol like http, httprest "request/response" (synchronous protocol) or mqtt "publish/subscribe" (asynchronous protocol), depending on needs [67]; (iii) fine-grained microservices, it is fundamental to decompose each service focused on a specific function and of limited influence, according to the established requirements [75]; otherwise, this architecture suffers from a high level of abstraction and coordination among the teams [67], [76].…”
Section: Discussionmentioning
confidence: 99%
“…2) Central orchestrator approach [9] where services are unaware of each other but post the events to a central orchestrator which takes care of firing the relevant actions in the destination services. This can be seen in Fig.…”
Section: Although This Technique Work For Limited Use Cases It Has the Following Challengesmentioning
confidence: 99%
“…Cluster can be called a group of similar objects, and clustering is a process of making similar sets out of raw data, which helps in segregation of unknown data easily. The parameters involved should be used cautiously as incompatible use of parameters of clustering like, Number of Clusters (k-means) and Density Limit, may lead to situations like improper density shape of clusters, ambiguity in finding centroid and the noise [5][6][7]. Mainly The improved semi supervised K mean clustering is used for the greedy iteration to find the K mean clustering is presented in [8].…”
Section: Introductionmentioning
confidence: 99%