MétaCan
Menu
Back to cohort
Record W4404132930 · doi:10.1109/access.2024.3492138

SliceSphere: Agile Service Orchestration and Management Framework for Cloud-Native Application Slices

2024· article· en· W4404132930 on OpenAlexaff
Pooyan Habibi, Alberto Leon‐Garcia

Bibliographic record

VenueIEEE Access · 2024
Typearticle
Languageen
FieldComputer Science
TopicService-Oriented Architecture and Web Services
Canadian institutionsUniversity of Toronto
Fundersnot available
KeywordsOrchestrationCloud computingAgile software developmentComputer scienceProcess managementSoftware engineeringOperating systemBusiness

Abstract

fetched live from OpenAlex

We introduce SliceSphere a comprehensive framework to ease the deployment and management of scalable cloud-native application slices. Slicesphere integrates a strong slicing framework with containerized orchestration engines. We present cloud-native application slicing as an architectural framework that integrates application segmentation, platform abstraction, and cloud-native methodologies into a system known as SliceSphere. This approach forms a cohesive, distributed application environment that surpasses traditional infrastructure limits, allowing organizations to deploy, manage, and scale applications across various computing landscapes with flexibility, scalability, and efficiency. In SliceSphere, each slice, termed SliceKube, operates as an independent unit, encompassing specific features and interacting via well-defined APIs. We have incorporated fundamental microservice design principles and offer extensive service integration, covering everything from specialized multi-stack control planes to essential resources such as computing power, storage, and networking. SliceSphere is built to be flexible, ensuring compatibility regardless of the orchestration engine or infrastructure provider in use. It simplifies complex deployments while enabling users to customize the design of control plane and platform service functionalities to their needs. Additionally, SliceSphere includes two marketplaces that offer pre-configured service-oriented applications and multi-cloud shared resources. A practical demonstration of SliceSphere, designed as a Kubernetes plugin and utilizing open-source technologies, has been developed on the multi-tiered SAVI infrastructure, leveraging a variety of resources. We examine this specific use case, SAVI 2.0, in detail to showcase SliceSphere’s ability to address the needs of distributed cloud-native applications across multi-tier and multi-cloud infrastructure.

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 distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.000
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Theoretical or conceptual · Consensus signal: Theoretical or conceptual
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.859
Threshold uncertainty score0.968

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0000.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0000.000
Scholarly communication0.0010.001
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.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.022
GPT teacher head0.321
Teacher spread0.299 · 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 teacher head, not a consensus.

The models applied no category: nothing in the taxonomy fit this work.
Study designTheoretical or conceptual
Domainnot available
GenreMethods

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

Citations3
Published2024
Admission routes1
Has abstractyes

Explore more

Same venueIEEE AccessSame topicService-Oriented Architecture and Web ServicesFrench-language works237,207