Industry Practices and Challenges for the Evolvability Assurance of Microservices.¶
Bogner, J., Fritzsch, J., Wagner, S., & Zimmermann, A. (2021). Industry Practices and Challenges for the Evolvability Assurance of Microservices. Empirical Software Engineering, 26(5).
Cited by¶
1 citation across 1 artifact.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Garbage Collection
- A team facing 412 microservices, 70 believed obsolete, treats the problem as garbage collection rather than opinion: the resource pool is the service inventory; the declared root set is every public API, every paying feature, and every regulatory commitment; the reference relation is the call graph (service A is live if something live calls it); the Closure is the transitive set of services reachable from a root by following calls; and the collectible set is the unmarked complement.
This sourceDocuments practitioner use of service dependency/call-graph analysis to identify and decommission microservices no longer reachable from committed consumer surfaces.
Supported in partVerified against the publisher's abstract
The abstract surveys microservice evolvability practice and calls for tooling to evaluate service granularity and dependencies, but states no garbage-collection framing, root set, closure, or service counts.
“specialized techniques, tools, and metrics are needed to support industry with the continuous evaluation of service granularity and dependencies”
- A team facing 412 microservices, 70 believed obsolete, treats the problem as garbage collection rather than opinion: the resource pool is the service inventory; the declared root set is every public API, every paying feature, and every regulatory commitment; the reference relation is the call graph (service A is live if something live calls it); the Closure is the transitive set of services reachable from a root by following calls; and the collectible set is the unmarked complement.
Verification¶
Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.
Does it back the claim? Read against the text for 1 of 1 citation: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Registry ID ref:8e7c535f7325 · see in the full table