A Black-box Monitoring Approach to Measure Microservices Runtime Performance
Abstract
Domain fit: Niche / domain-specific · No strong AI-core implementation/artifact signals were detected from current providers.
Microservices changed cloud computing by moving the applications’ complexity from one monolithic executable to thousands of network interactions between small components. Given the increasing deployment sizes, the architectural exploitation challenges, and the impact on data-centers’ power consumption, we need to efficiently track this complexity. Within this article, we propose a black-box monitoring approach to track microservices at scale, focusing on architectural metrics, power consumption, application performance, and network performance. The proposed approach is transparent w.r.t. the monitored applications, generates less overhead w.r.t. black-box approaches available in the state-of-the-art, and provides fine-grain accurate metrics.
Results and benchmarks
Microservices changed cloud computing by moving the applications’ complexity from one monolithic executable to thousands of network interactions between small components.
Benchmark evidence is limited
Evidence graph: 2 refs, 1 links.
Utility signals: depth 65/100, grounding 58/100, status medium.
Implementation
No direct implementation yet
Maintained implementation evidence is not confirmed for this paper yet.
Use the implementation status and reproduction sections for the current action plan.
No verified maintained repo yet
There is no verified maintained implementation yet. Use this baseline plan to decide whether to prototype now or defer.
- No direct maintained implementation was found. Use the paper PDF and citation graph to design a baseline reproduction.
- Start from related paper: Research of Microservices Features in Information Systems Using Spring Boot.
- Track assumptions and missing details in an experiment log before coding.
Time to first repro: a few days
Recommendation evidence is currently too limited for a maintained-repo choice. Use Implementation Status and Reproduction Path for a practical baseline plan.
- Estimate is based on paper-only reproduction flow
Reproduction readiness
No repo
No verified implementation available
- No maintained repository has been identified for this paper. Check adjacent implementations or HF artifacts below.
Hardware requirements
- Expect multi-day setup/compute for meaningful reproduction based on current guidance.
Validation caveat
Hugging Face artifacts
No trustworthy direct or curated related Hugging Face artifacts were found yet. Use targeted searches to quickly locate candidate models, datasets, and demos.
Datasets
Spaces
Tip: start with models, then check datasets and spaces if you need evaluation data or demos.
Research context
43
Citations
22
References
Tasks
Microservices, Computer science, Executable, Black box, Overhead (engineering), Software deployment, Cloud computing, Distributed computing
Methods
None detected
Domains
Power (physics)
Related papers
- Research of Microservices Features in Information Systems Using Spring BootSearch on Paper2Code
2020 · Semantic similarity
- Building an EdTech Platform Using Microservices and DockerSearch on Paper2Code
2021 · Semantic similarity
- Practical Efficient Microservice AutoscalingSearch on Paper2Code
2023 · Semantic similarity
- Design and implementation of dynamic microservice discovery solution in cloud architecturesSearch on Paper2Code
2017 · Semantic similarity
- Microservices with Spring CloudSearch on Paper2Code
2019 · Semantic similarity
- Towards a Technique for Extracting Microservices from Monolithic Enterprise SystemsSearch on Paper2Code
2016 · Semantic similarity
Open this paper in HFEPX to review benchmark signals, evaluation modes, and human-feedback protocol context.
Open in HFEPXJump to Paper2Code search queries derived from this paper's research context.