Gremlin: Systematic Resilience Testing of Microservices
The DOI matches its Crossref record.
Abstract
Modern Internet applications are being disaggregated into a microservice-based architecture, with services being updated and deployed hundreds of times a day. The accelerated software life cycle and heterogeneity of language runtimes in a single application necessitates a new approach for testing the resiliency of these applications in production infrastructures. We present Gremlin, a framework for systematically testing the failure-handling capabilities of microservices. Gremlin is based on the observation that microservices are loosely coupled and thus rely on standard message-exchange patterns over the network. Gremlin allows the operator to easily design tests and executes them by manipulating inter-service messages at the network layer. We show how to use Gremlin to express common failure scenarios and how developers of an enterprise application were able to discover previously unknown bugs in their failure-handling code without modifying the application.
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
Cited by
Zhou, X., Peng, X., Xie, T., Sun, J., Ji, C., Li, W., & Ding, D. (2021) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2018.2887384 · Cited by 410
“The existing research focuses on a wide range of topics about microservices, including design [11], testing [3], [12], [13], [14], deployment [15], [16], [17], verification [18], composition [19], architecture recovery [20], legacy migration [21], and runtime adaptation [22].”
Graph-based root cause analysis for service-oriented and microservice architectures
Brandón, Á., Solé, M., Huélamo, A., Solans, D., Pérez, M. S., & Muntés-Mulero, V. (2020) · Journal of Systems and Software · doi:10.1016/j.jss.2019.110432 · Cited by 121
“Following the same line of work, Gremlin [35] presents a framework for testing the resilience of microservices, allowing the user to design test scenarios that are translated into anomalies injected in the network.”
BackgroundMethodDetecting anomalies in microservices with execution trace comparison
Meng, L., Ji, F., Sun, Y., & Wang, T. (2021) · Future Generation Computer Systems · doi:10.1016/j.future.2020.10.040 · Cited by 70
Workflow-Aware Automatic Fault Diagnosis for Microservice-Based Applications With Statistics
Wang, T., Zhang, W., Xu, J., & Gu, Z. (2020) · IEEE Transactions on Network and Service Management · doi:10.1109/tnsm.2020.3022028 · Cited by 54
Yu, G., Huang, Z., & Chen, P. (2023) · Journal of Software: Evolution and Process · doi:10.1002/smr.2413 · Cited by 44
MicroRAS: Automatic Recovery in the Absence of Historical Failure Data for Microservice Systems
Wu, L., Tordsson, J., Acker, A., & Kao, O. (2020) · 2020 IEEE/ACM 13th International Conference on Utility and Cloud Computing (UCC) · doi:10.1109/ucc48980.2020.00041 · Cited by 14
“Several investigations have focused on resiliency patterns in microservices design [4], [5] and testing [6], [7].”
BackgroundImpactTracer: Root Cause Localization in Microservices Based on Fault Propagation Modeling
Xie, R., Yang, J., Li, J., & Wang, L. (2023) · 2023 Design, Automation & Test in Europe Conference & Exhibition (DATE) · doi:10.23919/date56975.2023.10137078 · Cited by 13
A Taxonomy of Integration-Relevant Faults for Microservice Testing
Gregor, L., Hentschel, A., Kastner, L., & Pretschner, A. (2025) · 2025 IEEE Conference on Software Testing, Verification and Validation (ICST) · doi:10.1109/icst62969.2025.10989000 · Cited by 5
Metadata
- Authors
- Heorhiadi, V., Rajagopalan, S., Jamjoom, H., Reiter, M. K., & Sekar, V.
- Venue
- 2016 IEEE 36th International Conference on Distributed Computing Systems (ICDCS)
- Publisher
- IEEE
- Published
- 2016-06
- Pages
- 57-66
- OpenAlex
- W2516734073
- Cited by
- 134
- References
- 0
- FWCI
- 10.03
- 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.