Service Mesh: Challenges, State of the Art, and Future Research Opportunities
The DOI matches its Crossref record; 5 of the 5 references it cites were found in a registry or an index.
Abstract
While the technology development towards microservices can significantly improve the speed and agility of software service delivery, it also raises the operational complexity associated with modern applications. This has led to the emergence of Service Mesh, a promising approach to mitigate this situation by introducing a dedicated infrastructure layer over microservices without imposing modification on the service implementations. Aiming to inspire more practical research work in this exploited area, we in this paper present a comprehensive review on the state of the art of Service Mesh and discuss the related challenges and its adoption. Finally, we highlight the opportunities for future research in this subject.
Overview
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Free: it reads the open-access text and checks the first 5 claims that cite a source we can check. Create a free account to check every claim.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Edge computing: Vision and challenges
Shi, W., Cao, J., Zhang, Q., Li, Y., & Xu, L. (2016) · IEEE Internet of Things Journal · doi:10.1109/jiot.2016.2579198 · Cited by 8,733
The vision of autonomic computing
Kephart, J. O., & Chess, D. M. (2003) · Computer · doi:10.1109/mc.2003.1160055 · Cited by 6,572 · cited 1×
“Publications Year Focus [20] 2018 Promoting Service Mesh [29] 2018 Microservices Governance [16] 2018 Using Service Mesh to Support IoT Cloud Application [30] 2018 Architectural Solution for Edge Environments [15] 2018 Service Mesh supported MAPE [31] loop control”
Method(2011) · doi:10.5555/1972457.1972488 · Cited by 1,619
Microservices Architecture Enables DevOps: Migration to a Cloud-Native Architecture
Balalaie, A., Heydarnoori, A., & Jamshidi, P. (2016) · IEEE Software · doi:10.1109/ms.2016.64 · Cited by 735 · cited 2×
“As presented in Table I, for example, rather than on-premises design, modern applications are more commonly to be designed with cloud-native [1] architectures, enabling executions in orchestrated environments.”
BackgroundOrchestration of Microservices for IoT Using Docker and Edge Computing
Alam, M., Rufino, J., Ferreira, J., Ahmed, S. H., Shah, N., & Chen, Y. (2018) · IEEE Communications Magazine · doi:10.1109/mcom.2018.1701233 · Cited by 188 · cited 1×
“On the other hand, the rising adoption of container technologies [45], [46] and microservices methodology [47], [48] in edge computing [49], has indicated the need and trend of exploration of service mesh in this area as the merging applications running on edge clouds are expected to be designed cloud-natively.”
Background
Cited by
Toward Context-Aware Anomaly Detection for AIOps in Microservices Using Dynamic Knowledge Graphs
Moens, P., Steenwinckel, B., Ongenae, F., Volckaert, B., & Hoecke, S. V. (2026) · IEEE Transactions on Network and Service Management · doi:10.1109/tnsm.2026.3652304 · Cited by 6
“A service mesh is a dedicated infrastructure layer that can be added to the application to enable features, such as observability (e.g., network tracing), traffic management (e.g., load balancing), and security [38].”
Metadata
- Authors
- Li, W., Lemieux, Y., Gao, J., Zhao, Z., & Han, Y.
- Venue
- 2019 IEEE International Conference on Service-Oriented System Engineering (SOSE)
- Publisher
- IEEE
- Published
- 2019-04
- Pages
- 122-1225
- OpenAlex
- W2944096373
- Cited by
- 185
- References
- 5
- FWCI
- 18.47
- Type
- conference paper
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.