2021
DOI: 10.1016/j.jss.2021.111014
|View full text |Cite
|
Sign up to set email alerts
|

Deployment and communication patterns in microservice architectures: A systematic literature review

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
37
0
1

Year Published

2022
2022
2024
2024

Publication Types

Select...
4
3

Relationship

0
7

Authors

Journals

citations
Cited by 62 publications
(38 citation statements)
references
References 23 publications
0
37
0
1
Order By: Relevance
“…In the case of the Single Instance Per Host and the Multiple Instances Per Host, a Host can be either a physical or a virtual machine (VM). The most popular deployment pattern, both in industry and academia, is the Single Instance Per Container, followed by the Single Instance Per Host, where a host is a VM [28]. There are several reasons why containers are preferred over VMs [28]: (i) creating and launching container images are often very fast, (ii) the same physical server can hold more containers than VMs due to their size, and (iii) more than one container can use a single operating system, which in turn reduces the overhead of licensing costs compared to the VM.…”
Section: Msa Design Patternsmentioning
confidence: 99%
See 1 more Smart Citation
“…In the case of the Single Instance Per Host and the Multiple Instances Per Host, a Host can be either a physical or a virtual machine (VM). The most popular deployment pattern, both in industry and academia, is the Single Instance Per Container, followed by the Single Instance Per Host, where a host is a VM [28]. There are several reasons why containers are preferred over VMs [28]: (i) creating and launching container images are often very fast, (ii) the same physical server can hold more containers than VMs due to their size, and (iii) more than one container can use a single operating system, which in turn reduces the overhead of licensing costs compared to the VM.…”
Section: Msa Design Patternsmentioning
confidence: 99%
“…With RPC, microservices can communicate either in a synchronous or asynchronous manner, whereas with Messaging the communication is always asynchronous. According to Aksakalli et al [28], it is not possible to determine the most popular communication pattern, since the selected pattern can change over time as the system evolves.…”
Section: Msa Design Patternsmentioning
confidence: 99%
“…At the backend, an orchestra of Celery [42] workers and Spark [43] jobs are deployed to offer microservices such as resource management, data management, data processing, and many others. Communication between Celery's microservice workers takes place over message-oriented middleware based on AMQP [44]. The core also includes a MongoDB [45] database which keeps records of all edge stations operating in the remote facilities.…”
Section: Core Infrastructurementioning
confidence: 99%
“…Energies 2022, 15, x FOR PEER REVIEW 7 of 20 over message-oriented middleware based on AMQP [44]. The core also includes a Mon-goDB [45] database which keeps records of all edge stations operating in the remote facilities.…”
Section: Core Infrastructurementioning
confidence: 99%
See 1 more Smart Citation