https://xgu5.github.io/tag/dependencies.html Dependencies Wowchemy (https://wowchemy.com)en-usMon, 26 Feb 2024 00:00:00 +0000 https://xgu5.github.io/media/icon_hu_a4f3f82829f42164.png https://xgu5.github.io/tag/dependencies.html https://xgu5.github.io/project/execution_dependencies.html Mon, 26 Feb 2024 00:00:00 +0000 https://xgu5.github.io/project/execution_dependencies.html <div class="container"> <div class="row justify-content-center align-items-center"> <div class="col-md-10 text-center"> <img src="../../img/Dependencies/Blocking_Effects.png" alt="Cross path blocking effects in microservices" class="m-0 w-100 img-fluid rounded"/> <h4 class="mt-1 mb-3">Figure 1. Blocking effects among different execution paths. Resource saturation in a single service can cascade across multiple execution paths, causing severe performance damage.</h4> </div> </div> <p class="text-start"> Microservice applications decompose monolithic business logic into loosely coupled microservices, introducing complex inter-service dependencies. This architectural shift poses a significant challenge to maintaining system-wide performance stability: resource contention in a single microservice can cascade, causing blocking effects cross different execution paths. As a result, <b>performance degradation from <a href="../../project/transition_bottlenecks.html">transient bottlenecks</a> in a microservice is not limited to its own execution path but instead propagates across multiple execution paths</b>, leading wide-spread performance degradation. </p> <div class="row justify-content-center align-items-center"> <div class="col-md-12 text-center"> <img src="../../img/Dependencies/CTQO.png" alt="Cross-service queue blocking" class="m-2 img-fluid rounded"/> <h4 class="mt-1 mb-3">Figure 2. Conceptual illustration of cross-service queue blocking.</h4> </div> </div> <p class="text-start"> Execution blocking occurs when resource saturation happens directly on a shared upstream microservice. In such a scenario, the shared upstream microservice becomes a bottleneck, blocking the execution of all dependent downstream microservices across different execution paths. However, cross-service queue blocking is more challenging to detect and mitigate because the resource saturation and the blocking effect occur on different microservices. In such a scenario, resource saturation can happen on any downstream microservice (DM) in one execution path and block the execution of other execution paths. </p> </div>