Jun 2026· Asian journal of mathematics and computer research· Vol 33, pp. 174-192· 0 citations
TL;DR
A critical narrative review of the academic literature on the technical foundations of containerization, its orchestration through platforms such as Kubernetes, and its relationship with two closely associated movements in contemporary software engineering: DevOps and microservices architecture suggests that Docker's importance lies less in any single technical innovation than in its function as a standardising artefact that lowered the practical threshold for adopting distributed, service-oriented and automation-intensive delivery models.
Abstract
Software containerization has changed how applications are built, packaged, deployed and operated, and Docker has been the principal force behind that change. This article presents a critical narrative review of the academic literature on the technical foundations of containerization, its orchestration through platforms such as Kubernetes, and its relationship with two closely associated movements in contemporary software engineering: DevOps and microservices architecture. The review traces the conceptual line from hypervisor-based virtualization to lightweight, operating-system-level isolation, then examines the empirical evidence on performance, resource efficiency, security and organisational adoption. Particular attention falls on how container technology has served as an enabling substrate for continuous integration and delivery pipelines, for the decomposition of monolithic systems into independently deployable services, and for the extension of cloud-native practice into edge, Internet of Things and serverless settings. The review also engages critically with contested claims in this literature, including the durability of reported performance advantages, the persistence of security and supply-chain risk, and the uneven evidence base behind many widely repeated benefits of DevOps and microservices adoption. The synthesis suggests that Docker's importance lies less in any single technical innovation than in its function as a standardising artefact that lowered the practical threshold for adopting distributed, service-oriented and automation-intensive delivery models. The article closes by identifying gaps in empirical rigour, a shortage of longitudinal and industrial-scale studies, and promising directions including container security taxonomies, AI-assisted operations and the convergence of serverless and container paradigms.
This paper explores the integration of Spring Boot with containerization and observability, focusing on best practices, architectural patterns, and challenges, and delves into containerization strategies using Docker and orchestration with Kubernetes, emphasizing their roles in deployment and scalability.
Youssef- Al-Habib, Omar Sullaiman· International Journal of Art...· 1 citation
Cloud-native architecture has been the new paradigm in enterprise application development that facilitates organization to reach unprecedented levels of scalability, agility, reliability, and operational efficiency. The dynamic business requirements, short delivery cycles of software solutions and the necessity of globally distributed services are mounting an increasing challenge on traditional monolithic systems. The concepts of microservices architecture, containerization, DevOps culture, and continuous delivery pipelines are the main principles in cloud-native systems that circumvent the limitations. This paper will be a detailed study of cloud-native architecture and its strategic role in a digital transformation process of businesses. Scalability models, distributed resource management, service orchestration, elasticity patterns and resilience techniques applied by cloud-native platforms are further detailed in the abstract. We address the transformation of enterprise application infrastructure out of on-premise legacy resource setting into service-based cloud environments properly configured to scale horizontally. The paper also investigates that the container orchestration systems such as Kubernetes make deployment, scaling, and failover operations to be declaratively automated. The purpose of service mesh, API-oriented architecture, event-based systems, policy-oriented autoscaling, and infrastructure-as-code (IaC) are examined to show how the architectural resilience and operational administration are accomplished. An approach to assess the maturity of cloud-native systems is presented based on the performance benchmarking, lifecycle automation, security compliance, and cost optimization indicators as part of a methodological framework. Also, the paper presents experimental evaluations of the response time, throughput, service resiliency, and infrastructure utilization in both traditional and cloud-native deployments. Findings indicate the application availability, frequency of deployment and scalability efficiency are very high. Lastly, such challenges as state management, data consistency, complexities in migrating, observability, and operational complexity are also addressed. The innovations that are emphasized by the best practices and future-oriented thinking include serverlesscomputing, auto-scaling that is run with AI, workloads based on WebAssembly, and automated cloud operations. All in all, the paper points to the idea that cloud-native architectures are not something the enterprises can afford to ignore on their quest towards maintaining competitive viability in the rapidly changing digital economy.
Kanya Mohammed, Naree Thongchai· International Journal of Mod...· 0 citations
Results indicate that organizations adopting microservices design on Kubernetes can achieve higher deployment frequency, better resiliency, improved resource utilization and greater agility to respond to evolving market needs.
Srichandra Boosa· American International Journ...· 0 citations
This paper presents a realistic case study showing how the implementation of DevOps principles in cross-functional teams, with the help of the standardized pipelines and integrated automation, facilitates cooperation, reduces cycle times, enhances quality assurance and accelerates delivery outcomes.
Karthik Allam· International Journal of Eme...· 0 citations
As legacy application architectures can limit the ability to deliver quickly, engineer for resilience, scale, and deploy independently, enterprise migration to microservices running on Kubernetes has emerged as a key modernization priority. This review analyzes peer-reviewed research in the field of migration patterns, service decomposition, containerization, orchestration, technical debt, organizational readiness and runtime governance in enterprise contexts. The literature suggests that full architectural replacement is seldom the most effective migration path. Instead, incremental extraction, a well-defined service-boundary understanding, platform engineering capability, observability maturity, data ownership redesign, and a staged coexistence between legacy and cloud-native elements are essential for durable modernization. Reported studies also highlight current shortcomings, such as poor longitudinal evidence, inconsistent migration measures, only minimal empirical validation for Kubernetes, and inadequate attention to regulated enterprise constraints. The review builds an abbreviated conceptual framework for migration to Kubernetes and draws inferences from comparative results from reported studies. It concludes that there needs to be more evidence in the field on production-scale economics of migration, platform reliability, socio-technical governance, and measurable results in different and diverse enterprise domains.
Shubham Srivastava· World Journal of Advanced En...· 0 citations
This paper presents a systematic, practice-driven evaluation of WebAssembly (WASM) as an execution substrate for cloud-native workloads orchestrated through Docker and Kubernetes using runwasi. We develop a reproducible workflow that compiles Rust and Go/TinyGo applications to WASM modules, applies Ahead-of-Time (AOT) optimizations per engine and architecture, and packages minimal OCI artifacts for multi-architecture deployment (amd64, arm64, riscv64). Through controlled experiments on heterogeneous nodes, we benchmark eight CPU-bound workloads, reporting mean, median, and confidence intervals to ensure statistical robustness. The results show that WASM achieves latencies close to native on amd64/arm64, with WasmEdge leading under AOT and Wasmtime offering strong compatibility and stability. Artifact sizes are substantially smaller than traditional containers, improving pull times and packing density. While riscv64 execution is feasible, it remains less mature and more sensitive to engine and build choices. Overall, the findings demonstrate that WASM is a viable and efficient option for Cloud Continuum environments when deployments rely on AOT-optimized artifacts, RuntimeClass-based scheduling, and workloads aligned with the WASI feature set supported by the selected engines.
Álvaro Vázquez-Rodríguez, David Vila-Pérez, Carlos Giraldo-Rodíguez et al.· International Conference on...· 0 citations