MétaCan
Menu
Back to cohort

Microservices Upgrade in Clouds: Dynamic Management of Version Dependencies and User Load

2024· article· en· W4405935633 on OpenAlexaff
Azadeh Azhdari, Amin Ebrahimzadeh, Carla Mouradian, R. Szabó, Roch Glitho

Bibliographic record

Venuenot available
Typearticle
Languageen
FieldComputer Science
TopicSoftware System Performance and Reliability
Canadian institutionsEricsson (Canada)Concordia University
Fundersnot available
KeywordsMicroservicesComputer scienceUpgradeConfiguration Management (ITSM)DatabaseOperating systemCloud computingDistributed computingComputer network

Abstract

fetched live from OpenAlex

In today's cloud computing environments, where scalability, agility, and resiliency are paramount, microservices architecture stands out as a fundamental keystone of modern software development. While microservices are designed as independent components communicating through well-defined APIs, maintaining and upgrading them pose unique challenges, including version compatibility, dependency management, and service continuity. These challenges become intricate when multiple instances of a specific microservice are deployed, utilizing load balancing to distribute users and offering different functionalities simultaneously. This paper proposes a heuristic algorithm to address the microservices upgrading problem. The proposed algorithm migrates users gradually and effectively by managing version dependencies, user load, considering propagation impact, multiple instances, and resource constraints. The simulation results demonstrate the superiority of our algorithm over existing benchmarks in terms of resource usage cost and the number of new version instances.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

How this classification was reachedexpand

Full frame machine prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.

metaresearch head score (Codex)0.001
metaresearch head score (Gemma)0.003
Version: metacan-v3-hybrid-931329e0061cValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.009
Threshold uncertainty score0.019

Distilled classifier scores by category (both heads)

CategoryCodexGemma
Metaresearch0.0010.003
Meta-epidemiology (narrow)0.0010.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.001
Science and technology studies0.0010.001
Scholarly communication0.0010.002
Open science0.0020.001
Research integrity0.0010.001
Insufficient payload (model declined to judge)0.0010.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.005
GPT teacher head0.235
Teacher spread0.230 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it

Classification

machine, unvalidated

Machine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designSimulation or modeling
Domainnot available
GenreEmpirical

How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".

Quick stats

Citations0
Published2024
Admission routes1
Has abstractyes

Explore more

Same topicSoftware System Performance and ReliabilityFrench-language works237,207