What, Where, When, How and Right of Runtime Adaptation in Service-Oriented Systems

State of runtime adaptation in service‐oriented systems: what, where, when, how and right

“…The what , when and how defined by Hirschfield et al relate adaptation to system properties, software development stages, and tools to effect adaptation. This is different from our classification, which relates what , where , when and how , and right to change triggers, application context, adaptation model and validation [11]. Our classification is supported by a recent review of the state of runtime adaptation in SOSs reveal that there are other important factors (dimensions) such as the application context, adaptation triggers, and validation.…”

“…The influencing factors are used as basis for reviewing 29 approaches intended to support runtime adaptation in service-oriented systems. The survey compliments existing surveys and extends our earlier survey [72] to include an in-depth review of runtime validation in service-oriented systems.…”

“…The lack of mechanisms for validating adaptation makes it difficult to gauge the appropriateness and effectiveness of adaptation decisions and limit our understanding of the nature of problems for which they are suited. Validation provides an avenue for adaptation rules to evolve and remain relevant because the factors that influence adaptation are constantly changing [11]. Validating adaptation goes beyond verifying that the adaptation conforms to its operational specification.…”

QoS-aware Autonomic Adaptation of Microservices Placement on Edge Devices

“…A possible option is to consider the architectural model for a microservice based application as a composition of services. We therefore studied Service oriented Architecture (SoA) adaptation solutions reviewed in (Mutanu and Kotonya, 2018). These solutions commonly include network QoS parameters in the criteria for selecting the optimal service location (Cardellini et al, 2017) (Aschoff and Zisman, 2011).…”