2018
DOI: 10.1007/978-3-319-74313-4_8
|View full text |Cite
|
Sign up to set email alerts
|

Microservices: How To Make Your Application Scale

Abstract: The microservice architecture is a style inspired by serviceoriented computing that has recently started gaining popularity and that promises to change the way in which software is perceived, conceived and designed. In this paper, we describe the main features of microservices and highlight how these features improve scalability.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
79
0
8

Year Published

2018
2018
2022
2022

Publication Types

Select...
4
4

Relationship

2
6

Authors

Journals

citations
Cited by 120 publications
(87 citation statements)
references
References 13 publications
0
79
0
8
Order By: Relevance
“…Also, the micro-services approach is implemented to digital curation infrastructure by devolving function into a set of micro-services which grants the deployment flexibility and simplify of the development and the maintenance [27]. These features of the micro-services architectures deal with the new trends of the HPC middleware [5], and ensure the scalability of the distributed applications [28].…”
Section: B Resultsmentioning
confidence: 99%
“…Also, the micro-services approach is implemented to digital curation infrastructure by devolving function into a set of micro-services which grants the deployment flexibility and simplify of the development and the maintenance [27]. These features of the micro-services architectures deal with the new trends of the HPC middleware [5], and ensure the scalability of the distributed applications [28].…”
Section: B Resultsmentioning
confidence: 99%
“…) for All in do (iterate Microservice instance being used) (7) for All ∈ do (check CVO and VOs used by the Services) (8) if O == output of C in a relationship set R then (9) add C to Ç (10) else (11) if O == output of V in relationship set R V then (12) add V to Ç (13) N ← tag (Assign relationship tag to each object entry) (14) else (15) add O to Ç (16) end if (17) end if (18) …”
Section: Social Relationship Discovery and Compositionmentioning
confidence: 99%
“…(1) Output: C (Composite Service) (2) AEM ← List all objects available (Microservices, CVOs, VOs) in model (3) ← executeQueryStatement (AEM, ) (4) Z ← executeQueryStatement (AEM, ) (5) for All ∈ do (6) for All ∈ do (7) if == any in Z then (8) add to Ç Lm (9) store Ç Lm (10) end if (11) end for (12) for All i ∈ Ç Lm do (13) if i == any i in Ç Lm then (14) ← ranking (Assign rank to each service) (15) add i to Ç LR (16) store Ç LR (17) end if (18) end for (19) for All ∈ Ç LR do (20) if (R ) > then (21) add to Wf (22) Pq ← assign to queue (23) Sort Pq (24) Formulate Wf (25) end if (26) as AEM is loaded, the first step is to compose objects based on their relationship types. This way, the SPARQL queries are executed; the first query is denoted as to retrieve the available service templates and the second query is represented as to extract the relationships associated with the services.…”
Section: Require: (Aec) (R ) (Z)mentioning
confidence: 99%
See 1 more Smart Citation
“…Monolithic system is a centralized architectural style of information system. The problem will occur when the demand to the system by the user are beyond the threshold level of how the system can handle and the centralized style of system has the problem to scale and to load balance the system gracefully [9].…”
Section: Related Workmentioning
confidence: 99%